CVE
WP Abstracts privilege escalation to administrator in AJAX form handler
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 18/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
The WP Abstracts plugin for WordPress has a privilege escalation flaw that lets a logged-in user with basic subscriber-level access raise their account to administrator. It can be reached remotely over the network by any account with that low level of login, and the attacker needs no action from anyone else.
Written by a model from the sources below. Verify against them.
Original description
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.
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.8/10CVSS 8.8, total technical impact per CISA
- No patch5/5No patch listed yet
What would change the score
- Would score about 73 if added to CISA KEV
- Would score about 68 if CISA's SSVC rates exploitation active
- Would score about 37 if advisories confirm default setups are exposed
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-12239 (WP Abstracts <= 2.7.6 - Authenticated (Subscriber+) Privilege Escalation via wpabs_save_regform AJAX Action), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-12239 (entry last updated 2026-11-17):
Affected:
- kevonadonis WP Abstracts: through 2.7.6
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-12239 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-12239 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/290e5e77-7d99-41df-b7d9-4e14b09c8e7a?source=cve
- https://plugins.trac.wordpress.org/browser/wp-abstracts-manuscripts-manager/tags/2.7.5/inc/wpabstracts_functions.php#L880
- https://plugins.trac.wordpress.org/browser/wp-abstracts-manuscripts-manager/tags/2.7.5/inc/wpabstracts_functions.php#L1140
- https://plugins.trac.wordpress.org/browser/wp-abstracts-manuscripts-manager/tags/2.7.5/users/html/users.profile.php#L7
- https://plugins.trac.wordpress.org/browser/wp-abstracts-manuscripts-manager/tags/2.7.5/inc/wpabstracts_functions.php#L872
- https://plugins.trac.wordpress.org/changeset/3781922/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-12239
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-12239"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- kevonadonis WP Abstracts
through 2.7.6
Evidence 8
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 6
- Link
- Link
- Link
- Link
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-12239
Is CVE-2026-12239 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-12239?
WP Abstracts: through 2.7.6.Source: cve.now feed data