Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach public form-submission AJAX endpoint
-
DeliverySubmit malicious formString payload unauthenticated
-
ExploitPayload stored without sanitization
-
ExecutionAdmin views form entries page
-
PersistScript executes in admin session
-
ImpactHijack session or create admin user
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitable without authentication against DEFAULT configurations: the nonce/authentication check on the rednao_smart_forms_save_form_values AJAX handler is enforced only when the non-default smart_forms_block_anonymous_submissions option is enabled, so default installs accept stored payloads from anyone. Prerequisite for the attack to achieve impact: a privileged user (typically an administrator) must subsequently view the page or form-entries view where the unsanitized formString is rendered, which is the main limiting factor. Enabling smart_forms_block_anonymous_submissions mitigates the unauthenticated path by restoring nonce verification. Affects all versions up to and including 2.6.104. |
| Impact | This is a genuine, elevated-priority issue for affected sites rather than a paper-tiger high-CVSS finding, primarily because of the unauthenticated access path. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N, base 7.2) aligns with the description: the nonce check on the rednao_smart_forms_save_form_values AJAX handler is only enforced when smart_forms_block_anonymous_submissions is enabled, so default installations accept and store attacker-supplied formString payloads with no authentication or nonce. The scope-changed metric (S:C) reflects that injected scripts execute in the browser context of whoever views the injected page, typically an administrator reviewing form entries, which can lead to session/account compromise despite the modest C:L/I:L impact rating. No EPSS score, CISA KEV listing, or public proof-of-concept was provided in the intelligence, so exploitation status is 'no public exploit identified at time of analysis' - this tempers urgency but does not eliminate it, since stored XSS in a no-auth-by-default WordPress plugin is a well-understood and easily weaponized class. The main caveat: the primary signal is a single vendor (Wordfence) report with no independent corroboration, no EPSS, and no confirmed fix version in the provided data, so remediation planning should verify the patched release directly with the plugin author. |
| Exploit ScenarioDerived | An unauthenticated attacker sends a crafted request to the rednao_smart_forms_save_form_values AJAX endpoint on a default Smart Forms installation, submitting a malicious JavaScript payload in the formString parameter, which is stored without sanitization. When a site administrator later opens the form entries view, the stored script executes in their authenticated browser session, enabling cookie/session theft or admin actions. No public proof-of-concept was provided in the available intelligence. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Stored cross-site scripting in the WordPress plugin Smart Forms - When You Need More Than Just a Contact Form (all versions up to and including 2.6.104) lets unauthenticated attackers inject arbitrary JavaScript through the 'formString' parameter, which is persisted and later executed in the browser of any user, typically an administrator, who views the affected page or the form-entries listing. The nonce and authentication check on the rednao_smart_forms_save_form_values AJAX handler is enforced only when the non-default smart_forms_block_anonymous_submissions option is enabled, so default installations accept and store malicious payloads from anyone with network access. No public exploit code has been identified at time of analysis, but the unauthenticated access path, low attack complexity, and scope-changing admin-context execution make this an elevated-priority issue for affected sites; impact still depends on a privileged user subsequently rendering the stored payload.
RemediationAI
No vendor-released patch was identified in the available data at time of analysis, and the Trac references point to unpatched trunk code rather than a fixed release, so confirmation of a corrected version should be obtained from the vendor/advisory page (https://www.wordfence.com/threat-intel/vulnerabilities/id/ace194b6-c794-417c-9870-db8ebaa4cf7a?source=cve) before assuming any upgrade resolves the issue. The most direct compensating control is to enable the plugin's smart_forms_block_anonymous_submissions option, which restores nonce verification on the rednao_smart_forms_save_form_values handler and closes the unauthenticated submission path; the trade-off is that legitimate anonymous (logged-out) form submissions will be blocked or rejected, which may break public-facing forms. Where anonymous submissions are essential, deploy a WAF/reverse-proxy rule that inspects POSTs to admin-ajax.php with action=rednao_smart_forms_save_form_values and rejects or sanitizes payloads containing HTML/script markup in the formString parameter - trade-off is potential false positives on forms that legitimately accept rich text, and evasion via encoding variants. Until a fix is available, also consider temporarily deactivating the plugin on sites that do not require it, restricting access to the WordPress admin entries screen to trusted users, and auditing existing stored form entries for injected script content, since previously stored payloads will continue to fire after any server-side mitigation. Enforcing a strict Content-Security-Policy that disallows inline script execution can reduce the practical impact of stored payloads but will not remove them and may break other admin-area functionality.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability is a CWE-79 improper neutralization of input during web page generation (stored/persistent XSS) in the WordPress plugin distributed under the slug 'smart-forms', attributed in CPE as cpe:2.3:a:edgarrojas:smart_forms_-_when_you_need_more_than_just_a_contact_form. User-supplied form data is accepted by the plugin's AJAX entry point (rednao_smart_forms_save_form_values, defined around smart-forms-ajax.php line 227 and registered/enqueued near smartforms.php line 63) and written to the database via the 'formString' parameter without adequate sanitization, then rendered back without output escaping in the administrative entries view - the referenced Entries_bundle.js lines (388, 588, 802) are the front-end rendering paths where the unescaped value is consumed. The critical structural weakness is the guard logic: the nonce/authorization check on that AJAX handler only runs when the smart_forms_block_anonymous_submissions setting is enabled, which is not the default, so on stock installations the handler is reachable with no authentication and no nonce verification. The CVSS:3.1 vector AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N is consistent with this design: network-reachable, unauthenticated, no user interaction on the attacker's side, and scope-changed because script executing in the privileged admin/entries context crosses a trust boundary, while confidentiality and integrity impacts remain limited rather than total.
Know when Wordpress Plugin gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
Default installs need no auth or nonce (PR:N/AC:L), payload stored remotely (AV:N), executes automatically on page view crossing into victim browser context (S:C, UI:N), typical XSS C:L/I:L/A:N.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Smart Forms - when you need more than just a contact form plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'formString' parameter in all versions up to, and including, 2.6.104 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 nonce check protecting the rednao_smart_forms_save_form_values AJAX handler is only enforced when the smart_forms_block_anonymous_submissions option is enabled, meaning default installations require no authentication or nonce verification whatsoever to submit and store malicious payloads.
Executive ViewAI
The Smart Forms WordPress plugin (all versions up to and including 2.6.104) has a high-severity stored cross-site scripting issue that can persist malicious JavaScript and execute it in the browsers of administrative users who view affected pages or form entries. No public exploit identified at time of analysis, but successful exploitation could lead to administrator session compromise, unauthorized site changes, data theft, or full site takeover, making this an elevated priority for any organization hosting affected WordPress sites. Leadership should care because default installations may accept payloads from network-accessible attackers, and no vendor-released patch identified at time of analysis.
No vendor-released patch identified at time of analysis. Interim mitigations: disable the Smart Forms plugin until a fixed version is available, or if it must remain active, enable the non-default smart_forms_block_anonymous_submissions option to enforce nonce and authentication checks; restrict access to the form-entries listing and wp-admin to trusted IPs; deploy WAF rules to block JavaScript in the formString parameter; monitor logs for suspicious submissions; enforce least privilege and multi-factor authentication for administrative users.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
Remote code execution in the WP Query Console WordPress plugin (versions up to and including 1.0) by Ajit Bohra allows u
EUVD-2026-100794
GHSA-wvww-4x5h-8gg3
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB