Security readout for executives and security teams
Plain-English summary
CVE-2026-2707 is a stored cross-site scripting issue in the WordPress weForms plugin through version 1.6.27. A logged-in low-privilege user could submit malicious content through the REST API that later runs in an administrator’s browser when form entries are viewed.
Executive priority
Treat as a moderate-priority WordPress plugin issue. Prioritize sites with public registration, customer portals, or many low-privilege users because successful exploitation targets administrator sessions and could enable data exposure or unauthorized actions in the admin context.
Technical view
The flaw is inconsistent sanitization between frontend AJAX submissions and the REST API entry submission endpoint. REST requests can bypass the expected cleaning path, leaving hidden field values only trimmed. Entry data is later rendered with Vue v-html, allowing stored script execution in the admin form entries interface.
Likely exposure
Exposure is most relevant to WordPress sites running weForms version 1.6.27 or earlier, especially sites allowing public registration, subscriber accounts, or many low-privilege users. Sites without untrusted authenticated users have lower practical exposure.
Exploitation context
The CVE is not listed in KEV, and the provided sources do not state active exploitation. Exploitation requires authenticated access at Subscriber level or higher and depends on an administrator viewing affected form entries.
Researcher notes
The provided affected metadata is inconsistent, but the CVE narrative and Wordfence reference state versions up to 1.6.27 are affected. A code change and GitHub pull request are referenced, but the supplied sources do not clearly name a fixed release.
Mitigation direction
- Identify WordPress sites using the weForms plugin.
- Check whether installed weForms versions are 1.6.27 or earlier.
- Review Wordfence, vendor, GitHub, and WordPress plugin guidance for fixed release details.
- Restrict untrusted Subscriber-level access where possible until remediated.
- Limit access to form entry administration pages to trusted administrators.
Validation and detection
- Inventory weForms installations and record plugin versions.
- Confirm whether public user registration or untrusted subscriber accounts are enabled.
- Review form entry handling and REST API exposure against vendor guidance.
- Check administrative logs for unusual entry submissions by low-privilege users.
- Track the referenced GitHub pull request and WordPress changeset for remediation status.
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-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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 lookupCVE-2026-2707 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
- Medium
- CVSS
- 6.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
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.
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:L/UI:N/S:C/C:L/I:L/A:N3.12.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/e97854ca-b24f-4893-862d-f8e975752175?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/weforms/tags/1.6.27/includes/fields/class-abstract-fields.php#L542CVE reference
- https://plugins.trac.wordpress.org/browser/weforms/tags/1.6.27/assets/js-templates/spa-components.php#L80CVE reference
- https://plugins.trac.wordpress.org/browser/weforms/trunk/includes/fields/class-abstract-fields.php#L542CVE reference
- https://plugins.trac.wordpress.org/browser/weforms/trunk/assets/js-templates/spa-components.php#L80CVE reference
- https://github.com/BoldGrid/weforms/pull/263CVE reference
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&new=3475812%40weforms%2Ftrunk&old=3457241%40weforms%2Ftrunk&sfp_email=&sfph_mail=CVE reference
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 Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
