CVE-2026-127115 · Package
NO FIX YET · SEE WHAT TO DO
The BuddyForms WordPress plugin does not sanitize the buddyforms_form_content parameter, so an unauthenticated visitor can store a script on a page. The script runs in the browser of anyone who opens that page.
first public Nov 14, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Sites running the BuddyForms WordPress plugin up to and including 2.10.6 that publish a form with the public_submit option, which the bundled Post Simple template does by default. Sites without BuddyForms or without a published public_submit form are not exposed through this flaw.
Not affected if no-buddyforms, no-public-submit-form
Who cares buddyforms, wordpress
wp plugin get buddyforms --field=version2.10.6 are affected; the sources do not state a fixed versionThe BuddyForms plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'buddyforms_form_content' parameter in all versions up to, and including, 2.10.6 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. This is exploitable when a form configured with the public_submit option is published — a condition met by the plugin's bundled Post Simple template out of the box.
This page as .md · .json · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.