Skip to main content

Paid Membership Subscriptions EUVDEUVD-2026-85195

| CVE-2026-90950 MEDIUM
Protection Mechanism Failure (CWE-693)
2026-09-23 WPScan GHSA-4p9q-3q6w-vc23
5.3
CVSS 3.1 · Vendor: WPScan
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify PMS registration form with reCAPTCHA
  2. Exploit
    Craft registration POST omitting reCAPTCHA field
  3. Execution
    Handler skips verification
  4. Impact
    Create unauthenticated accounts at scale

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V15 - Secure Coding and Architecture Protection mechanism completeness
Exploitation Conditions

Exploitable only when the site runs Paid Membership Subscriptions before version 3.1.0 AND has the reCAPTCHA feature enabled on its registration form. The core prerequisite is that the registration handler fails to verify reCAPTCHA when the reCAPTCHA form field is absent from the request, so the attacker simply omits that field. No authentication and no user interaction are required (AV:N/PR:N/UI:N), but the limiting factor is configuration-specific: sites without reCAPTCHA enabled gain nothing to bypass, and the only outcome is unsolved-CAPTCHA account registration, not data access or code execution.

Impact

This is a low-severity protection-mechanism-bypass, not a high-impact flaw. The CVSS 3.1 base of 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) reflects remote, unauthenticated, low-complexity access with no user interaction, but the real-world impact is narrow: an attacker can register accounts without solving the site's reCAPTCHA by omitting the expected form field. Exploitation status is 'publicly available exploit code exists' - WPScan (the reporter) publishes a vulnerability entry flagged as an exploit - but this is NOT active exploitation: no CISA KEV listing and no EPSS score were provided, so widespread or targeted in-the-wild use is unconfirmed. Note a signal conflict: the vendor vector claims C:L (confidentiality), yet the description describes a reCAPTCHA/anti-automation bypass enabling unauthorized account creation, which is functionally an integrity/abuse issue with no data disclosure - the C:L attribution is questionable and the 'Information Disclosure' tag is inaccurate. Net: a real but low-priority hardening bug (spam/bot-registration exposure), not an urgent RCE-class threat.

Exploit ScenarioDerived

An attacker sends automated registration requests to a Paid Membership Subscriptions form (v < 3.1.0) that has reCAPTCHA enabled, deliberately omitting the reCAPTCHA form field so the handler skips verification entirely. This lets bots mass-create member accounts without solving any challenge; a public WPScan exploit entry documents the technique.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 23, 2026

Missing reCAPTCHA verification in the Paid Membership Subscriptions WordPress plugin before version 3.1.0 lets unauthenticated attackers create user accounts without solving the CAPTCHA the site has enabled, by simply omitting the reCAPTCHA form field from the registration request. Publicly available exploit code exists (documented by WPScan), though there is no confirmed active exploitation per CISA KEV. The impact is a protection-mechanism bypass rather than data exposure or code execution - the assessed vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N - and it only affects sites that run an affected version and have reCAPTCHA enabled on the registration form.

RemediationAI

Upgrade Paid Membership Subscriptions to version 3.1.0 or later; that is the vendor-released patched version and the only fix identified in the available data, and it can be applied through the standard WordPress plugin update mechanism or by installing the tagged release from the plugin repository. If immediate upgrade is not possible, the exposure is limited to sites with reCAPTCHA enabled on the registration form, so the most direct compensating control is to close the registration path entirely - disable public/open registration or the plugin's front-end registration form - which stops automated account creation but also prevents legitimate self-service signups for the duration. A secondary option is to front the registration endpoint with rate limiting, a WAF rule, or an alternate anti-automation mechanism (for example a challenge or CAPTCHA enforced at the edge rather than inside the plugin), understanding that this only raises the cost of bulk registration and does not restore the broken in-plugin check, since an attacker who omits the field will still bypass the plugin's own verification. Monitor the WPScan advisory at https://wpscan.com/vulnerability/685f381e-97b5-4855-a0ca-5854043a7b9e/ for any revised affected-version range or additional mitigation guidance, and audit existing user accounts for anomalous bulk registrations if an affected configuration was exposed.

Affected VersionsENISA

Paid Membership Subscriptions 2.0.5 <3.1.0

Affected Packages

euvd paid_membership_subscriptions fix: 3.1.0

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 affected component is the WordPress membership/registration plugin Paid Membership Subscriptions, identified in the supplied CPE data as cpe:2.3:a:unknown:paid_membership_subscriptions:*:*:*:*:*:*:*:* (vendor field unresolved in the feed, so track updates via the WPScan advisory rather than a CPE match). The plugin integrates Google reCAPTCHA as an anti-automation control on its registration handler, but the verification logic is conditional on the presence of the reCAPTCHA response field in the incoming request. When that field is absent, the handler skips verification entirely and proceeds to create the account, so the client effectively controls whether the server-side security check runs. No CWE was supplied with the CVE record; the root-cause class is best characterized as missing server-side validation of an anti-automation control (the CWE-804/CWE-602 family of CAPTCHA and client-side-enforcement weaknesses) rather than a memory-safety, injection, or authorization-model flaw. Successful abuse yields only the ability to register an account without solving a CAPTCHA - the practical consequence is automated bulk account creation and the loss of bot mitigation, which is why the assessed impact is integrity-only with no confidentiality or availability effect.

Know when Paid Membership Subscriptions 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

Vendor (WPScan) PRIMARY 5.3 MEDIUM
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
vuln.today AI 5.3 MEDIUM

Remote unauthenticated low-complexity bypass; impact is unauthorized account creation (integrity, I:L) with no data disclosure (C:N) or availability loss (A:N).

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

Lifecycle Timeline

2
Patch available
Sep 23, 2026 - 11:17 EUVD
CVE Published
Sep 23, 2026 - 10:11 cve.org
MEDIUM 5.3

DescriptionCVE.org

The Paid Membership Subscriptions WordPress plugin before 3.1.0 does not verify the reCAPTCHA on its registration handler when a form field is absent from the request, allowing unauthenticated users to create accounts without solving the reCAPTCHA the site has enabled.

Threat Intelligence Overview

EPSS Score
0.2%
Top 91% exploitable
Prevalence
Medium
popular Cozmoslabs WordPress membership plugin, tens of thousands of installs
Exploit
POC
Public exploit code exists
Data Quality
4 sources
Confidence: Medium

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.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC Yes
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

46
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy