WP Abstracts <= 2.7.2 - Cross-Site Request Forgery to Reflected Cross-Site Scripting
Strategic Overview
- Status
- Patched in 2.7.3
- Affected Plugin
- WP Abstracts
- Affected Version
<= 2.7.2- CVSS
- 6.1Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2024-12385
At a glance
CVE-2024-12385 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP Abstracts WordPress plugin, affecting versions <= 2.7.2. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.7.3; sites on affected versions should update now. Disclosed January 2025, reported by vgo0.
Vulnerability Overview
The WP Abstracts plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.7.2. This is due to missing nonce validation on the wpabstracts_load_status() and wpabstracts_delete_abstracts() functions. This makes it possible for unauthenticated attackers to inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
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.
CWE-352: Cross-Site Request Forgery (CSRF)
WP Abstracts <= 2.7.2 carries this weakness at wpabstracts_load_status(), and reaching it 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 Abstracts the fix is 2.7.3: builds <= 2.7.2 are affected, anything from 2.7.3 onward is not.
Remediation
Update to version 2.7.3, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to WP Abstracts: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Abstracts 2.7.3 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in WP Abstracts
- 8.1CVE-2025-48338: Abstracts <= 2.7.4 Local File Inclusion
CVE-2025-48338 - 6.1CVE-2023-29385: WP Abstracts <= 2.6.1 Reflected Cross-Site Scripting
CVE-2023-29385 - 4.4CVE-2024-50411: WP Abstracts <= 2.7.1 Stored Cross-Site Scripting
CVE-2024-50411 - 4.4CVE-2024-44045: WP Abstracts <= 2.6.5 Stored Cross-Site Scripting
CVE-2024-44045 - 4.4CVE-2023-28692: WP Abstracts <= 2.6.2 Stored Cross-Site Scripting
CVE-2023-28692
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C