CVE-2021-25073

WP125 <= 1.5.4 - Cross-Site Request Forgery to Arbitrary Ad Deletion

2021-12-23 00:00

Strategic Overview

Status: Patched in 1.5.5
Affected Plugin: WP125
Affected Version: <= 1.5.4
CVSS: 8.8High
Weakness type: CWE-352 · Cross-Site Request Forgery (CSRF)
CVE: CVE-2021-25073

At a glance

CVE-2021-25073 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP125 WordPress plugin, affecting versions <= 1.5.4. 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.5.5; sites on affected versions should update now. Disclosed December 2021, reported by Krzysztof Zając.

Vulnerability Overview

The WP125 WordPress plugin before 1.5.5 does not have CSRF checks in various action, for example when deleting an ad, allowing attackers to make a logged in admin delete them via a CSRF attack

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 WP125 <= 1.5.4 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 WP125 the fix is 1.5.5: builds <= 1.5.4 are affected, anything from 1.5.5 onward is not.

Remediation

Update to version 1.5.5, or a newer patched version

How does WordSec protect against this?

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

Firewall
Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2021-25073 https://www.wordfence.com/threat-intel/vulnerabilities/id/6263e0cd-5843-444d-8d12-61a898a77724 https://nvd.nist.gov/vuln/detail/CVE-2021-25073

Related records

Same weakness class

8.8CVE-2013-2700: WP125 <= 1.4.9 Cross-Site Request ForgeryCVE-2013-2700

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/