Security readout for executives and security teams
Plain-English summary
This issue affects older WP Security Audit Log WordPress plugin installations before version 1.2.5. A CSRF flaw could let an attacker abuse a logged-in victim’s browser to perform unintended plugin-related actions. The public record does not specify the exact action, impact, or victim role required.
Executive priority
Treat this as a targeted cleanup item for legacy WordPress assets, not a confirmed emergency. Prioritize internet-facing sites and any high-value WordPress administration environments because public exploit material is referenced.
Technical view
CVE-2014-5072 is a CSRF vulnerability in WP Security Audit Log before 1.2.5 for WordPress. The CVE describes authentication hijacking of unspecified victims through unknown vectors. No CVSS, CWE, or detailed affected CPE data is provided in the source bundle.
Likely exposure
Exposure is limited to WordPress sites that installed WP Security Audit Log versions earlier than 1.2.5. The source bundle does not confirm affected configurations, required privileges, or whether current successor versions remain relevant.
Exploitation context
CISA KEV status is false, and the supplied sources do not show active exploitation. A public GitHub exploit reference exists, which raises validation urgency, but the bundle does not provide enough detail to assess real-world exploitability.
Researcher notes
The public CVE data is sparse: unknown vector, unspecified victims, no CVSS, no CWE, and no CPEs. Analysis should avoid assuming impact beyond CSRF-based authenticated action abuse until vendor notes or historical exploit details are reviewed.
Mitigation direction
- Inventory WordPress sites for WP Security Audit Log plugin versions below 1.2.5.
- Upgrade affected installations to version 1.2.5 or later per vendor guidance.
- If upgrade is unavailable, disable or remove the outdated plugin.
- Review the vendor changelog for version-specific remediation notes.
- Restrict WordPress administrator access while remediation is pending.
Validation and detection
- Confirm installed plugin name and version from WordPress admin or asset inventory.
- Check whether any site runs WP Security Audit Log before 1.2.5.
- Review administrative audit logs for unexpected plugin setting changes.
- Verify remediation by confirming the plugin version after update or removal.
- Track this finding separately if exact exposure cannot be proven.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2014-5072 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wpsecurityauditlog.com/plugin-change-log/CVE reference · x_refsource_CONFIRM
- https://github.com/0pc0deFR/Exploits/tree/master/CVE-2014-5072CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.