CVE-2026-2022

Smart Forms <= 2.6.100 - Missing Authorization to Authenticated (Subscriber+) Campaign Data Exposure

2026-02-13 18:31
lucsob

Strategic Overview

Status
Patched in 2.6.101
Affected Plugin
Smart Forms – when you need more than just a contact form
Affected Version
<= 2.6.100
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-2022
View all Smart Forms – when you need more than just a contact form vulnerabilities

At a glance

CVE-2026-2022 is a medium-severity Missing Authorization vulnerability in the Smart Forms WordPress plugin, affecting versions <= 2.6.100. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.6.101; sites on affected versions should update now. Disclosed February 2026, reported by lucsob.

Vulnerability Overview

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.100. This makes it possible for authenticated attackers, with Subscriber-level access and above, to retrieve donation campaign data including campaign IDs and names.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-862: Missing Authorization

Smart Forms <= 2.6.100 carries this weakness at rednao_smart_forms_get_campaigns, and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Smart Forms the fix is 2.6.101: builds <= 2.6.100 are affected, anything from 2.6.101 onward is not.

Remediation

Update to version 2.6.101, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Smart Forms 2.6.101 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-2022https://www.wordfence.com/threat-intel/vulnerabilities/id/381ec109-ca51-4011-b7e0-aec636540d59https://nvd.nist.gov/vuln/detail/CVE-2026-2022

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C