LiveActive security incident?Get immediate response
CVE Record

CVE-2026-2707: weForms <= 1.6.27 - Authenticated (Subscriber+) Stored Cross-Site Scripting via Hidden Field Value via REST API

The weForms plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the REST API entry submission endpoint in all versions up to, and including, 1.6.27. This is due to inconsistent input sanitization between the frontend AJAX handler and the REST API endpoint. When entries are submitted via the REST API (`/wp-json/weforms/v1/forms/{id}/entries/`), the `prepare_entry()` method in `class-abstract-fields.php` receives the WP_REST_Request object as `$args`, bypassing the `weforms_clean()` fallback that sanitizes `$_POST` data for frontend submissions. The base field handler only applies `trim()` to the value. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject arbitrary web scripts into form entry hidden field values via the REST API that execute when an administrator views the form entries page, where data is rendered using a Vue.js `v-html` directive without escaping.

MediumCVSS 6.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

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.
Prepared
Confidence
medium
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

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 lookup
cve · low confidence lookup

CVE-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
Vulnerability profileCVE Program record
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

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
8Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
6.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N3.12.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.4Medium
CVSS 3.1 vector shape for CVE-2026-2707Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
boldgridweForms – Easy Drag & Drop Contact Form Builder For WordPress0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-79 · source CWE mapping

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.