ARFORMS · CVE-2026-12424 · Package
NO FIX YET · SEE WHAT TO DO
The ARforms plugin for WordPress stores attacker-supplied content from the Referer header through an unauthenticated AJAX handler, without sanitizing or escaping it. When a user opens a page containing the stored payload, the attacker's JavaScript runs in that user's browser.
first public Nov 7, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Sites running the ARforms plugin for WordPress at version 7.2.4 or earlier are exposed, since the flawed AJAX handler accepts requests without logging in. Sites without this plugin are not affected.
Not affected if plugin-not-installed
Who cares arforms, self-hosted, wordpress
arf_save_incomplete_form_data handler in the plugin's code.7.2.4 are affected.The ARforms plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Referer Header in all versions up to, and including, 7.2.4 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. The arf_save_incomplete_form_data() AJAX handler is registered with wp_ajax_nopriv_, meaning unauthenticated attackers can store a malicious payload by submitting a partial form entry with a forged Referer header, with no authentication required at any step.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/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.
Check it with your coding agent
It reads this page and tells you if your code is affected.
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.