What is the CVSS score of CVE-2015-5488?

CVE-2015-5488 has a CVSS 2.0 base score of 2.1 (Low). CVSS vector: AV:N/AC:H/Au:S/C:N/I:P/A:N. EPSS exploitation probability: 0.2%.

Is there a patch available for CVE-2015-5488?

Yes, a patch is available for CVE-2015-5488. Update the affected software to the latest version immediately.

Mailchimp CVE-2015-5488

LOW

Cross-site Scripting (XSS) (CWE-79)

2015-08-18 cve@mitre.org

XSS Mailchimp

2.1

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

2.1 LOW

AV:N/AC:H/Au:S/C:N/I:P/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

AV:N/AC:H/Au:S/C:N/I:P/A:N

Attack Vector

Network

Attack Complexity

High

Confidentiality

None

Integrity

Availability

None

Lifecycle Timeline

CVE Published

Aug 18, 2015 - 17:59 cve.org

LOW 2.1

DescriptionCVE.org

Cross-site scripting (XSS) vulnerability in the MailChimp Signup submodule in the MailChimp module 7.x-3.x before 7.x-3.3 for Drupal allows remote authenticated users with the "administer mailchimp" permission to inject arbitrary web script or HTML via unspecified vectors.

AnalysisAI

Cross-site scripting (XSS) vulnerability in the MailChimp Signup submodule in the MailChimp module 7.x-3.x before 7.x-3.3 for Drupal allows remote authenticated users with the "administer mailchimp". Rated low severity (CVSS 2.1), this vulnerability is remotely exploitable.

Technical ContextAI

This vulnerability is classified as Cross-Site Scripting (XSS) (CWE-79), which allows attackers to inject malicious scripts into web pages viewed by other users. Cross-site scripting (XSS) vulnerability in the MailChimp Signup submodule in the MailChimp module 7.x-3.x before 7.x-3.3 for Drupal allows remote authenticated users with the "administer mailchimp" permission to inject arbitrary web script or HTML via unspecified vectors. Affected products include: Thinkshout Mailchimp. Version information: before 7..

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Sanitize all user input, use Content-Security-Policy headers, encode output contextually (HTML, JS, URL). Use frameworks with built-in XSS protection.