CVE-2026-120547 · Package
NO FIX YET
The CF7 Apps plugin for WordPress does not sanitize the honeypot tag value in Contact Form 7 form bodies, up to and including version 3.8.0. An authenticated user with custom-level access or above can store scripts that run in the browser of anyone who opens the injected page.
first public Nov 13, 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 CF7 Apps plugin at version 3.8.0 or earlier that let custom-level or higher users edit Contact Form 7 forms. The sources say the escalation matters most on multisite installs or sites with DISALLOW_UNFILTERED_HTML enabled, since Editors on default single-site installs already hold the unfiltered_html capability. Sites without the plugin, or without untrusted authenticated editors, are less exposed.
Not affected if no-untrusted-editors, plugin-not-installed
Who cares cf7-apps, contact-form-7, wordpress
3.8.0 or earlier in the WordPress plugins screen.DISALLOW_UNFILTERED_HTML is set to true in wp-config.php.No fix yet, per the sources.
The CF7 Apps – Honeypot, Database, Redirection, Webhook, and Addons for Contact Form 7 plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'wpcf7-form (CF7 form body; the [honeypot ...] tag value)' parameter in all versions up to, and including, 3.8.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with custom-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This is only a meaningful privilege escalation on multisite installations or those with DISALLOW_UNFILTERED_HTML enabled, as Editor-level users on default single-site installs already possess the unfiltered_html capability.
This page as .md · .json · CVSS:3.1/AV:N/AC:H/PR:H/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.