What is the CVSS score of CVE-2013-0320?

CVE-2013-0320 has a CVSS 2.0 base score of 5.1 (Medium). CVSS vector: AV:N/AC:H/Au:N/C:P/I:P/A:P. EPSS exploitation probability: 0.2%.

Is there a patch available for CVE-2013-0320?

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

Taxonomy Manager CVE-2013-0320

MEDIUM

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

2013-03-27 secalert@redhat.com

CSRF Taxonomy Manager

5.1

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

5.1 MEDIUM

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

High

Confidentiality

Integrity

Availability

Lifecycle Timeline

CVE Published

Mar 27, 2013 - 21:55 cve.org

MEDIUM 5.1

DescriptionCVE.org

Cross-site request forgery (CSRF) vulnerability in the Taxonomy Manager (taxonomy_manager) module 6.x-2.x before 6.x-2.2 and 7.x-1.x before 7.x-1.0-rc1 for Drupal allows remote attackers to hijack the authentication of users with 'administer taxonomy' permissions via unspecified vectors.

AnalysisAI

Cross-site request forgery (CSRF) vulnerability in the Taxonomy Manager (taxonomy_manager) module 6.x-2.x before 6.x-2.2 and 7.x-1.x before 7.x-1.0-rc1 for Drupal allows remote attackers to hijack. Rated medium severity (CVSS 5.1), 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 Taxonomy Manager (taxonomy_manager) module 6.x-2.x before 6.x-2.2 and 7.x-1.x before 7.x-1.0-rc1 for Drupal allows remote attackers to hijack the authentication of users with 'administer taxonomy' permissions via unspecified vectors. Affected products include: Mattias Hutterer Taxonomy Manager. Version information: before 6..

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.