CVE-2026-2707 json
weForms <= 1.6.27 - Authenticated (Subscriber+) Stored Cross-Site Scripting via Hidden Field Value via REST API
published 2026-03-11 7 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-11099
- cvss
- 6.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 15%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- github.com/BoldGrid/weforms#263 pull request
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 7 mo ago
Exploit prediction
0.24% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N |
Affected products
- boldgrid weForms – Easy Drag & Drop Contact Form Builder For WordPress
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- github.com /BoldGrid/weforms/pull/263
- wordfence.com /threat-intel/vulnerabilities/id/e97854ca-b24f-4893-862d-f8e975752175?source=cve
- plugins.trac.wordpress.org /browser/weforms/tags/1.6.27/includes/fields/class-abstract-fields.php#L542
- plugins.trac.wordpress.org /browser/weforms/tags/1.6.27/assets/js-templates/spa-components.php#L80
- plugins.trac.wordpress.org /browser/weforms/trunk/includes/fields/class-abstract-fields.php#L542
- plugins.trac.wordpress.org /browser/weforms/trunk/assets/js-templates/spa-components.php#L80
- plugins.trac.wordpress.org /changeset?sfp_email=&sfph_mail=&reponame=&new=3475812%40weforms%2Ftrunk&old=3457241%40weforms%2Ftrunk&sfp_ema
Sources
- CVE List CVE-2026-2707
- NVD CVE-2026-2707
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.