What is the CVSS score of CVE-2012-4421?

CVE-2012-4421 has a CVSS 2.0 base score of 4.0 (Medium). CVSS vector: AV:N/AC:L/Au:S/C:N/I:P/A:N. EPSS exploitation probability: 0.2%.

Is there a public PoC exploit available for CVE-2012-4421?

Yes, a public proof-of-concept exploit is available for CVE-2012-4421. Prioritise patching immediately. EPSS: 0.2%.

PHP CVE-2012-4421

MEDIUM

Permissions, Privileges, and Access Controls (CWE-264)

2012-09-14 secalert@redhat.com

PHP WordPress Privilege Escalation

4.0

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

4.0 MEDIUM

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Confidentiality

None

Integrity

Availability

None

Lifecycle Timeline

CVE Published

Sep 14, 2012 - 19:55 cve.org

MEDIUM 4.0

DescriptionCVE.org

The create_post function in wp-includes/class-wp-atom-server.php in WordPress before 3.4.2 does not perform a capability check, which allows remote authenticated users to bypass intended access restrictions and publish new posts by leveraging the Contributor role and using the Atom Publishing Protocol (aka AtomPub) feature.

AnalysisAI

The create_post function in wp-includes/class-wp-atom-server.php in WordPress before 3.4.2 does not perform a capability check, which allows remote authenticated users to bypass intended access. Rated medium severity (CVSS 4.0), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.

Technical ContextAI

This vulnerability is classified under CWE-264. The create_post function in wp-includes/class-wp-atom-server.php in WordPress before 3.4.2 does not perform a capability check, which allows remote authenticated users to bypass intended access restrictions and publish new posts by leveraging the Contributor role and using the Atom Publishing Protocol (aka AtomPub) feature. Affected products include: Wordpress. Version information: before 3.4.2.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Apply vendor patches when available. Implement network segmentation and monitoring as interim mitigations.