CVE-2014-5072

WP Activity Log <= 1.2.4 - Cross-Site Request Forgery

2014-08-01 00:00

Strategic Overview

Status: Patched in 1.2.5
Affected Plugin: WP Activity Log
Affected Version: < 1.2.5
CVSS: 8.8High
Weakness type: CWE-352 · Cross-Site Request Forgery (CSRF)
CVE: CVE-2014-5072

View all WP Activity Log vulnerabilities

At a glance

CVE-2014-5072 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP Activity Log WordPress plugin, affecting versions < 1.2.5. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.2.5; sites on affected versions should update now. Disclosed August 2014, reported by Kévin FALCOZ aka 0pc0deFR.

Vulnerability Overview

Cross-site request forgery (CSRF) vulnerability in WP Security Audit Log plugin before 1.2.5 for WordPress allows remote attackers to hijack the authentication of unspecified victims via unknown vectors.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

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

Reaching this weakness in WP Activity Log < 1.2.5 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For WP Activity Log the fix is 1.2.5: builds < 1.2.5 are affected, anything from 1.2.5 onward is not.

Remediation

Update to version 1.2.5, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to WP Activity Log: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Activity Log 1.2.5 closes this, and updating the plugin is the step that ends it.

Firewall
Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2014-5072 https://www.wordfence.com/threat-intel/vulnerabilities/id/2f025b73-9a1a-4890-90ef-700f73ac018f https://nvd.nist.gov/vuln/detail/CVE-2014-5072

Related records

Same weakness class

Other vulnerabilities in WP Activity Log

CVSS Vector

8.8

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionRequired
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/