Plugins · smart-forms · data as of 2026-11-04
Is Smart Forms safe? Known vulnerabilities and latest version
- Status
- Closed 2026-10-08
- Known issues on record
- 12
- Unpatched in latest
- 0
What to do
- Replace it. A closed plugin gets no updates through WordPress, so any hole found from now on stays open.
- Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deleting removes its files; deactivating alone leaves them on the server.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.
With WP-CLI, once you have a replacement: wp plugin deactivate smart-forms && wp plugin delete smart-forms
Check your version
Known vulnerabilities
12 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version. 12 record(s) do not state which versions are affected.
high 7.2 CVE-2026-95816 · published 2026-10-14
Stored cross-site scripting (XSS) in Smart Forms (2.6.104 and older)
- Affected
- 2.6.104 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
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.
high 7.1 CVE-2026-32574 · published 2026-10-06
Cross-site scripting (XSS) in Smart Forms (2.6.104 and older)
- Affected
- 2.6.104 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in EDGARROJAS Smart Forms smart-forms allows DOM-Based XSS.This issue affects Smart Forms: from n/a through 2.6.104.
medium 4.3 CVE-2026-2022 · published 2026-02-14
Missing authorization check in Smart Forms (2.6.99 and older)
- Affected
- 2.6.99 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The Smart Forms plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the 'rednao_smart_forms_get_campaigns' AJAX action in all versions up to, and including, 2.6.99. This makes it possible for authenticated attackers, with Subscriber-level access and above, to retrieve donation campaign data including campaign IDs and names.
medium 4.4 CVE-2025-5055 · published 2025-05-24
Stored cross-site scripting (XSS) in Smart Forms (2.6.98 and older)
- Affected
- 2.6.98 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- Needs an admin-level account
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The Smart Forms – when you need more than just a contact form plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and including, 2.6.98 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.
NVD CVE-2025-5055Wordfence advisoryCode change (fix)wordpress.org
high 8.8 CVE-2023-49856 · published 2024-12-09
Missing authorization check in Smart Forms (2.6.84 and older)
- Affected
- 2.6.84 and older
- Fixed in
- 2.6.85
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
Missing Authorization vulnerability in EDGARROJAS Smart Forms smart-forms allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Smart Forms: from n/a through <= 2.6.84.
medium 4.3 CVE-2024-33593 · published 2024-04-29
Missing authorization check in Smart Forms (2.6.91 and older)
- Affected
- 2.6.91 and older
- Fixed in
- 2.6.92
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
Missing Authorization vulnerability in RedNao Smart Forms.This issue affects Smart Forms: from n/a through 2.6.91.
medium 5.9 CVE-2024-1905 · published 2024-04-29
Stored cross-site scripting (XSS) in Smart Forms (older than 2.6.96)
- Affected
- older than 2.6.96
- Fixed in
- 2.6.96
- Access needed (per CVSS)
- Needs an admin-level account; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by CISA ADP
Details from the advisory
The Smart Forms WordPress plugin before 2.6.96 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup)
medium 5.4 CVE-2024-1306 · published 2024-04-15
Cross-site request forgery (CSRF) in Smart Forms (older than 2.6.94)
- Affected
- older than 2.6.94
- Fixed in
- 2.6.94
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by CISA ADP
Details from the advisory
The Smart Forms WordPress plugin before 2.6.94 does not have CSRF checks in some places, which could allow attackers to make logged-in users perform unwanted actions via CSRF attacks, such as editing entries, and we consider it a medium risk.
medium 6.5 CVE-2024-1307 · published 2024-04-15
Missing authorization check in Smart Forms (older than 2.6.94)
- Affected
- older than 2.6.94
- Fixed in
- 2.6.94
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by CISA ADP
Details from the advisory
The Smart Forms WordPress plugin before 2.6.94 does not have proper authorization in some actions, which could allow users with a role as low as a subscriber to call them and perform unauthorized actions
medium 6.1 CVE-2023-7203 · published 2024-02-27
Cross-site request forgery (CSRF) in Smart Forms (older than 2.6.87)
- Affected
- older than 2.6.87
- Fixed in
- 2.6.87
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by CISA ADP
Details from the advisory
The Smart Forms WordPress plugin before 2.6.87 does not have authorisation in various AJAX actions, which could allow users with a role as low as subscriber to call them and perform unauthorised actions such as deleting entries. The plugin also lacks CSRF checks in some places which could allow attackers to make logged in users perform unwanted actions via CSRF attacks such as deleting entries.
medium 6.5 CVE-2022-0163 · published 2022-03-07
Information disclosure in Smart Forms (older than 2.6.71)
- Affected
- older than 2.6.71
- Fixed in
- 2.6.71
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- NVD analysis · score by NVD
Details from the advisory
The Smart Forms WordPress plugin before 2.6.71 does not have authorisation in its rednao_smart_forms_entries_list AJAX action, allowing any authenticated users, such as subscriber, to download arbitrary form's data, which could include sensitive information such as PII depending on the form.
high 8.8 CVE-2019-5924 · published 2019-03-12
Cross-site request forgery (CSRF) in Smart Forms (2.6.15 and older)
- Affected
- 2.6.15 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- NVD analysis · score by NVD
Details from the advisory
Cross-site request forgery (CSRF) vulnerability in Smart Forms 2.6.15 and earlier allows remote attackers to hijack the authentication of administrators via a specially crafted page.
Recent activity
- 2026-10-08 — closed on wordpress.org.
- 2026-10-14 — Stored cross-site scripting (XSS) disclosed (CVE-2026-95816), fix version not stated.
- 2026-10-06 — Cross-site scripting (XSS) disclosed (CVE-2026-32574), fix version not stated.
- 2026-02-14 — Missing authorization check disclosed (CVE-2026-2022), fix version not stated.
Get an email when Smart Forms has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Smart Forms (smart-forms) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
Types found in this plugin: Cross-site scripting (XSS) (4) · Missing authorization (4) · Cross-site request forgery (CSRF) (3) · Sensitive data exposure (1)
Where this data comes from
- Version, last update, installs, closure: wordpress.org/plugins/smart-forms (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/smart-forms"><img src="https://laskyr.com/plugins/smart-forms/badge.svg" alt="Smart Forms vulnerability status"></a>