Security readout for executives and security teams
Plain-English summary
A public WordPress page using ASE Pro’s form shortcode can expose what an attacker needs to reach a vulnerable save function. An unauthenticated attacker could then run code on the server, potentially stealing data, changing the site, or disrupting service. The issue affects ASE Pro through version 8.9.0 when the stated shortcode condition exists.
Executive priority
Treat this as an immediate remediation priority for internet-facing sites meeting both exposure conditions. The vulnerability can permit full server-side code execution without credentials. Rapidly identify affected sites, contain the public form path, and investigate for compromise; however, do not claim an incident solely from vulnerability presence.
Technical view
The frontend handler relies on a publicly exposed nonce without authentication, while CAPTCHA enforcement can be bypassed by omission. Unsanitized repeater row keys from cfgroup[input] are stored and later inserted into an eval() call by recursive_html. Exploitation requires a publicly accessible page containing the [post_cf_form] shortcode. CVSS is 9.8.
Likely exposure
Internet-facing WordPress installations running ASE Pro 8.9.0 or earlier are exposed only if at least one public page contains [post_cf_form]. Sites without that shortcode condition are not described as reachable through this path. The bundle’s affected-version metadata is inconsistent, so confirm installed versions directly.
Exploitation context
The attack is remote, requires no authentication or user interaction, and has low stated complexity. Successful exploitation could compromise confidentiality, integrity, and availability. The CVE is not listed as KEV in the supplied bundle, and the supplied sources do not establish active exploitation in the wild.
Researcher notes
The decisive exposure chain is public shortcode output, unauthenticated save-handler access, bypassable CAPTCHA logic, verbatim repeater keys, and later eval() interpolation. The bundle names CWE-434, although its narrative specifically describes PHP code injection. No confirmed patched version, vendor fix, public exploit, or observed exploitation is established by the supplied evidence.
Mitigation direction
- Identify ASE Pro installations running version 8.9.0 or earlier.
- Remove or restrict public access to pages containing [post_cf_form].
- Disable the affected plugin where business operations permit.
- Check ASE and Wordfence guidance for a confirmed fixed release or vendor mitigation.
- Review potentially exposed sites for compromise before restoring functionality.
Validation and detection
- Confirm the installed ASE Pro version on every WordPress site.
- Inventory public pages and templates containing the [post_cf_form] shortcode.
- Verify affected pages are removed, restricted, or no longer publicly reachable.
- Review server, WordPress, and security logs for unexpected requests or code changes.
- Confirm remediation against current ASE or Wordfence guidance before re-enabling forms.
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-434: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. 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 lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-16610 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
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/2ef21a44-6d03-4197-b49c-d881f9831f46?source=cveCVE reference, Wordfence
- https://www.wpase.com/CVE 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.
Unrestricted Upload of File with Dangerous Type
Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.