CVE-2026-107658 json
BuddyForms <= 2.10.5 - Unauthenticated Stored Cross-Site Scripting via 'bf_post_type' Parameter via Post-Type Confusion
published 3d ago modified 3d ago also EUVD-2026-118198
- cvss
- 5.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 25%
- public exploits
- 0
- none known
Summary
The BuddyForms plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'bf_post_type (and buddyforms_form_content)' parameter in all versions up to, and including, 2.10.5 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires that at least one BuddyForms form with public submissions enabled exists on the site (so that the required nonce can be harvested from the public form page) and that the active theme registers a widgetized sidebar, allowing the injected customize_changeset to place a malicious Custom HTML widget into the site's front end.
Patch / fix
- github.com/Themekraft/buddyforms#779 pull request
Is CVE-2026-107658 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 3d ago
Exploit prediction
0.33% chance of exploitation in the next 30 days, higher than 25% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N |
Affected products
- themekraft BuddyForms
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- github.com /Themekraft/buddyforms/pull/779/files
- wordfence.com /threat-intel/vulnerabilities/id/ec36eff4-0f85-4d89-b209-aaf07ae2ff9c?source=cve
- plugins.trac.wordpress.org /browser/buddyforms/tags/2.10.2/includes/form/form-control.php#L642
- plugins.trac.wordpress.org /browser/buddyforms/tags/2.10.2/includes/form/form-ajax.php#L96
- plugins.trac.wordpress.org /browser/buddyforms/tags/2.10.2/includes/form/form-control.php#L258
- plugins.trac.wordpress.org /browser/buddyforms/tags/2.10.2/includes/form/form-control.php#L261
- plugins.trac.wordpress.org /browser/buddyforms/tags/2.10.2/includes/form/form-control.php#L359
- plugins.trac.wordpress.org /browser/buddyforms/tags/2.10.2/includes/form/form-control.php#L604
- plugins.trac.wordpress.org /changeset/3780268/buddyforms/trunk/includes/form/form-control.php
Sources
- CVE List CVE-2026-107658
- NVD CVE-2026-107658
Fencer Intel 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.