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

CVE-2015-3388 has a CVSS 2.0 base score of 5.8 (Medium). CVSS vector: AV:N/AC:M/Au:N/C:N/I:P/A:P. EPSS exploitation probability: 0.1%.

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

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

Commerce Balanced Payments CVE-2015-3388

MEDIUM

Cross-Site Request Forgery (CSRF) (CWE-352)

2015-04-21 cve@mitre.org

CSRF Commerce Balanced Payments

5.8

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

5.8 MEDIUM

AV:N/AC:M/Au:N/C:N/I:P/A:P

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

AV:N/AC:M/Au:N/C:N/I:P/A:P

Attack Vector

Network

Attack Complexity

Confidentiality

None

Integrity

Availability

Lifecycle Timeline

CVE Published

Apr 21, 2015 - 18:59 cve.org

MEDIUM 5.8

DescriptionCVE.org

Cross-site request forgery (CSRF) vulnerability in the Commerce Balanced Payments module for Drupal allows remote attackers to hijack the authentication of arbitrary users for requests that delete the user's configured bank accounts via unspecified vectors.

AnalysisAI

Cross-site request forgery (CSRF) vulnerability in the Commerce Balanced Payments module for Drupal allows remote attackers to hijack the authentication of arbitrary users for requests that delete. Rated medium severity (CVSS 5.8), this vulnerability is remotely exploitable.

Technical ContextAI

This vulnerability is classified as Cross-Site Request Forgery (CSRF) (CWE-352), which allows attackers to trick authenticated users into performing unintended actions. Cross-site request forgery (CSRF) vulnerability in the Commerce Balanced Payments module for Drupal allows remote attackers to hijack the authentication of arbitrary users for requests that delete the user's configured bank accounts via unspecified vectors. Affected products include: Balanced Commerce Balanced Payments.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Implement anti-CSRF tokens, validate Origin/Referer headers, use SameSite cookie attribute.