CVE-2026-24944
Missing Authorization in weDevs Subscribe2 Allows Unauthorized Access
Publication date: 2026-02-20
Last updated on: 2026-02-20
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| we_devs | subscribe2 | to 10.44 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-862 | The product does not perform an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability arises from missing authorization and authentication checks in the Subscribe2 WordPress plugin versions up to 10.44, allowing unauthenticated users to perform privileged actions.
Detection can involve monitoring for unauthorized access attempts or exploitation attempts targeting the Subscribe2 plugin functions.
Patchstack provides an automatic mitigation rule that blocks exploitation attempts, which can also be used to detect such attempts.
Specific commands are not provided in the available resources.
Can you explain this vulnerability to me?
CVE-2026-24944 is a medium priority Broken Access Control vulnerability in the WordPress Subscribe2 plugin versions up to and including 10.44.
The issue arises from missing authorization, authentication, or nonce token checks within certain plugin functions, which allows unauthenticated users to perform actions that should be restricted to higher privileged users.
This means that attackers can exploit incorrectly configured access control security levels to gain unauthorized privileges.
The vulnerability is classified under the OWASP Top 10 category A1: Broken Access Control.
How can this vulnerability impact me? :
This vulnerability allows unauthenticated users to perform actions reserved for privileged users, potentially leading to unauthorized privilege escalation.
Such unauthorized access can compromise the security and integrity of your WordPress site by allowing attackers to manipulate subscription-related functions without proper permissions.
Because no prior authentication is required, the risk of exploitation is higher, increasing the likelihood of unauthorized actions being performed.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
What immediate steps should I take to mitigate this vulnerability?
The primary mitigation step is to update the Subscribe2 WordPress plugin to version 10.45 or later, where the vulnerability has been patched.
Until the update can be applied, Patchstack offers an automatic mitigation rule that blocks exploitation attempts.
Enabling auto-updates for vulnerable plugins via Patchstack can also help ensure timely protection.