Appsero <= 2.0.0 - Missing Authorization via handle_optin_optout
Strategic Overview
- Status
- Patched in 10.43
- Affected Plugin
- Subscribe2 – Form, Email Subscribers & Newsletters
- Affected Version
<= 10.42- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-32110
At a glance
CVE-2024-32110 is a medium-severity Missing Authorization vulnerability in the Subscribe2 WordPress plugin, affecting versions <= 10.42. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 10.43; sites on affected versions should update now. Disclosed April 2024, reported by Dhabaleshwar Das.
Vulnerability Overview
The Appsero analytics tool used in several plugins is vulnerable to unauthorized modification of data due to a missing capability check on the handle_optin_optout function in versions up to, and including, 2.0.0. This makes it possible for unauthenticated attackers to opt-in or opt-out of tracking. This was patched in version 2.0.1 of Appsero with a nonce check.
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
Reaching this weakness in Subscribe2 <= 10.42 takes a caller who can reach the endpoint. 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 Subscribe2 the fix is 10.43: builds <= 10.42 are affected, anything from 10.43 onward is not.
Remediation
Update to version 10.43, 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: Subscribe2 10.43 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Subscribe2 – Form, Email Subscribers & Newsletters
- 7.2CVE-2026-73393: Subscribe2 Stored XSS
CVE-2026-73393 - 7.2CVE-2024-11582: Subscribe2 Stored XSS
CVE-2024-11582 - 7.1CVE-2022-4309: Subscribe2 <= 10.37 Cross-Site Request Forgery
CVE-2022-4309 - 7.1Subscribe2 – Form, Email Subscribers & Newsletters < 8.1 Multiple XSS
- 6.1CVE-2026-14331: Subscribe2 <= 10.45 Reflected Cross-Site Scripting
CVE-2026-14331 - 6.1CVE-2014-6604: Subscribe2 Stored XSS
CVE-2014-6604 - 4.3CVE-2023-3407: Subscribe2 <= 10.40 Cross-Site Request Forgery
CVE-2023-3407 - 4.3CVE-2022-47150: Appsero <= 1.2.0 Cross-Site Request Forgery
CVE-2022-47150
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C