WP Abstracts <= 2.7.6 - Authenticated (Subscriber+) Privilege Escalation via wpabs_save_regform AJAX Action
Strategic Overview
- Status
- Patched in 2.7.7
- Affected Plugin
- WP Abstracts
- Affected Version
<= 2.7.6- CVSS
- 8.8High
- Weakness type
- CWE-269 · Improper Privilege Management
- CVE
CVE-2026-12239
At a glance
CVE-2026-12239 is a high-severity Improper Privilege Management vulnerability in the WP Abstracts WordPress plugin, affecting versions <= 2.7.6. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.7.7; sites on affected versions should update now. Disclosed November 2026, reported by Nabil Irawan.
Vulnerability Overview
The WP Abstracts plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 2.7.6. This is due to a missing capability check on the wpabs_save_regform AJAX action and the use of a static, frontend-exposed nonce that allows any authenticated user to persist attacker-controlled form schemas with arbitrary wpSync mappings that are later used as user meta keys in the wpabstracts_sync_wpfields function. This makes it possible for authenticated attackers, with subscriber-level access and above, to elevate their privileges to administrator.
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 interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-269: Improper Privilege Management
Reaching this weakness in WP Abstracts <= 2.7.6 takes an account at Subscriber level or above. Improper privilege management means the code lets an account end up with capabilities its role should not have.
It converts a low-privileged account into an administrative one, which makes every other restriction on the site irrelevant. For WP Abstracts the fix is 2.7.7: builds <= 2.7.6 are affected, anything from 2.7.7 onward is not.
Remediation
Update to version 2.7.7, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: WP Abstracts 2.7.7 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in WP Abstracts
- 8.1CVE-2025-48338: Abstracts <= 2.7.4 Local File Inclusion
CVE-2025-48338 - 8.1CVE-2024-12386: WP Abstracts CSRF to Arbitrary Account Deletion
CVE-2024-12386 - 6.1CVE-2025-32591: WP Abstracts CSRF to Stored Cross-Site Scripting
CVE-2025-32591 - 6.1CVE-2024-12385: WP Abstracts CSRF to Reflected Cross-Site Scripting
CVE-2024-12385 - 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