Security readout for executives and security teams
Plain-English summary
An unauthenticated attacker may change a WordPress administrator’s email address through the affected plugin, then use WordPress password recovery to seize the account. Successful compromise could give the attacker control of site content, user data, configuration, and administrative functions.
Executive priority
Act immediately on internet-facing affected sites. Account takeover could rapidly become full administrative compromise. Identify affected installations, disable exposure or apply a vendor-confirmed fix, and investigate recent administrator email changes and password-reset activity.
Technical view
Frontend Admin by DynamiApps through 3.29.12 accepts crafted object identifiers targeting user records. The email update path lacks capability and ownership checks, while a non-numeric post identifier can bypass the edit_post authorization gate. This permits unauthenticated modification of user email addresses and subsequent account takeover through password reset.
Likely exposure
Internet-reachable WordPress sites running Frontend Admin by DynamiApps 3.29.12 or earlier should be treated as potentially exposed. Publicly accessible plugin forms increase concern. The supplied evidence does not fully define every configuration prerequisite, so administrators should validate installed versions and reachable forms directly.
Exploitation context
The weakness is network-accessible, requires no authentication or user interaction, and has a supplied CVSS 3.1 score of 9.8. The source bundle marks KEV as false and provides no evidence of active exploitation. That absence should not be interpreted as proof exploitation is not occurring.
Researcher notes
The core issue combines missing authorization in pre_update_value with authorization short-circuiting for non-numeric identifiers in ActionPost::conditions_logic(). The supplied WordPress Trac references and changeset support code-level review, but the bundle does not explicitly identify a fixed version or document observed exploitation.
Mitigation direction
- Check vendor guidance and upgrade only to a release explicitly confirmed to fix CVE-2026-75816.
- Disable the plugin or affected public forms until a confirmed fixed release is installed.
- Restrict access to affected form endpoints where operationally feasible.
- If compromise is suspected, revoke sessions and secure affected accounts after preserving evidence.
Validation and detection
- Inventory all WordPress sites and identify installations running version 3.29.12 or earlier.
- Confirm unauthenticated requests cannot modify user records in an authorized staging environment.
- Review administrator email-address changes, password-reset events, and unexpected privileged sessions.
- Inspect relevant web, WordPress, and security logs for suspicious unauthenticated form submissions.
- Verify the installed release contains the vendor’s authorization-check changes.
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.
CWE-287: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-75816 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
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9WordfenceVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- Source timelineWordfence
Vendor Notified
- Source timelineWordfence
Disclosed
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/f1637a3b-7b0f-485d-9d19-4f711f8c671b?source=cveCVE reference, Wordfence
- https://plugins.trac.wordpress.org/browser/acf-frontend-form-element/tags/3.29.10/main/frontend/fields/user/class-user-email.php#L127CVE reference, Wordfence
- https://plugins.trac.wordpress.org/browser/acf-frontend-form-element/tags/3.29.10/main/frontend/forms/actions/post.php#L1224CVE reference, Wordfence
- https://plugins.trac.wordpress.org/browser/acf-frontend-form-element/tags/3.29.10/main/frontend/forms/classes/display.php#L26CVE reference, Wordfence
- https://plugins.trac.wordpress.org/browser/acf-frontend-form-element/tags/3.29.10/main/frontend/forms/classes/submit.php#L125CVE reference, Wordfence
- https://plugins.trac.wordpress.org/changeset/3664865/acf-frontend-form-elementCVE reference, Wordfence
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.
Improper Authentication
Improper Authentication represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.