Skip to main content

Subscriptions for WooCommerce CVE-2026-87854

| EUVDEUVD-2026-80208 MEDIUM
Information Exposure (CWE-200)
2026-09-16 WPScan GHSA-mp62-wj23-fc7f
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 site running vulnerable plugin
  2. Delivery
    Send crafted request to REST endpoint
  3. Exploit
    Bypass improper shared-secret validation
  4. Execution
    Retrieve full subscription list
  5. Impact
    Harvest customer PII and billing data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK

2 techniques across 2 tactics: Collection, Discovery

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

No special conditions beyond running the affected software: the site must have the Subscriptions for WooCommerce plugin (WPSwings) installed and active at a version before 2.0.3, with the vulnerable REST endpoint reachable over the network. Exploitation is remote and unauthenticated (PR:N/UI:N) against default configurations because the endpoint's shared-secret protection is validated incorrectly and can be bypassed without valid credentials. Limiting factors: impact is confined to reading subscription data (confidentiality only - no write, privilege gain, or takeover), the store must actually use the subscriptions feature to hold meaningful data, and the flaw is fixed by updating to 2.0.3.

Impact

Signals are internally consistent and point to a genuine but moderate-severity data-exposure issue rather than a critical one. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, base 5.3) describes a network-reachable, low-complexity, fully unauthenticated flaw with confidentiality-only impact and no integrity or availability effect - appropriate for a broken access-control disclosure of aggregate customer PII. EPSS is low at 0.18% (8th percentile) and there is no CISA KEV listing, indicating no evidence of active or widespread exploitation. However, a public WPScan proof-of-concept exists, which raises the practical likelihood of opportunistic use against unpatched stores because the exploit is trivial (single crafted REST request, no auth, no user interaction). No signals conflict: the low EPSS alongside available POC is normal for a newly disclosed low-priority WordPress plugin bug - POC availability and exploitation probability are distinct, and low EPSS here reflects lack of observed mass exploitation, not lack of exploitability. Net: a real priority for stores handling recurring-billing customer data (privacy/GDPR exposure) but not a drop-everything critical, given confidentiality-only impact and no privilege or system compromise. The CPE lists vendor as 'unknown' and one tag is the placeholder 'Unknown' - metadata hygiene issues that do not affect the technical assessment.

Exploit ScenarioDerived

An unauthenticated attacker sends a crafted request to the plugin's protected REST endpoint, where the shared-secret check is validated incorrectly and can be bypassed. The endpoint returns the store's complete subscription dataset - customer usernames, product names, recurring amounts and payment dates - exposing sensitive customer and revenue data. A public WPScan proof-of-concept exists, and because the flaw is remote, unauthenticated, and low-complexity (AV:N/AC:L/PR:N/UI:N), exploitation requires only a single HTTP request against a vulnerable store.

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 17, 2026

Unauthenticated remote attackers can retrieve a WooCommerce store's complete subscription roster - customer usernames, product names, recurring amounts and payment dates - because the Subscriptions for WooCommerce plugin from WPSwings (all versions before 2.0.3) validates the shared secret protecting one of its REST endpoints incorrectly. The flaw is rated CVSS 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N), so exploitation requires no credentials or user interaction and is limited to confidentiality loss - no data modification, privilege escalation or account takeover - but the store must actually be using the plugin's subscriptions feature for meaningful data to be exposed. Publicly available exploit code exists (documented by WPScan), the CVE is not listed in CISA KEV, and EPSS is 0.18% (8th percentile), indicating low observed exploitation likelihood; the vendor has released a fixed version 2.0.3.

RemediationAI

Upgrade Subscriptions for WooCommerce to version 2.0.3 or later, which is the vendor-released fix for this issue; confirm the update on every site in the estate, since WordPress plugin auto-updates are frequently disabled on managed installations. Where an immediate update is not possible, the most effective compensating control is to block the plugin's REST namespace at the web server, reverse proxy or WAF - the exact route is documented in the WPScan advisory at https://wpscan.com/vulnerability/a47ee557-3036-485a-91ad-af7b84209294/ - with the caveat that blocking the whole /wp-json/ path will break unrelated WordPress functionality, so the rule must be scoped to that plugin's namespace, and any legitimate front-end feature that calls the same endpoint will stop working. If the store does not use subscriptions at all, deactivating and removing the plugin eliminates the exposure entirely, at the cost of losing subscription management and renewal/billing automation for any data already held (export it first). Log review for anomalous or high-volume GET requests to the plugin's REST namespace, and treating leaked username/product/pricing data as a disclosure that may feed credential-stuffing or social-engineering campaigns, are reasonable follow-ups; rotating any shared secret configured for the plugin is advisable once patched, since the old value should be considered untrusted. No vendor patch is noted as unavailable and no CISA KEV listing applies, so emergency out-of-band procedures are not mandated by the threat picture - EPSS is 0.18% (8th percentile).

Affected VersionsENISA

Subscriptions for WooCommerce 0 <2.0.3

Affected Packages

euvd subscriptions_for_woocommerce fix: 2.0.3

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 a WordPress plugin REST endpoint registered by Subscriptions for WooCommerce rather than a WordPress core API. Instead of relying on WordPress's standard REST authentication primitives (cookie plus nonce, application passwords, or capability checks such as current_user_can), the plugin gated this endpoint behind a custom 'shared secret' string. The validation logic is implemented incorrectly - the secret is compared or handled in a way that fails open - so a request supplying a malformed, empty or otherwise unverifiable secret is accepted, effectively producing an authorization bypass on a data-read route. The result is mapped to CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor): the response serializes subscription objects belonging to other customers, leaking usernames, product names, recurring billing amounts and payment dates. Because the endpoint is reachable over the network under the normal /wp-json/ routing surface and requires no session, the practical precondition is simply an internet-reachable WordPress installation with the vulnerable plugin active. The CPE string supplied in the intelligence feed (cpe:2.3:a:unknown:subscriptions_for_woocommerce:*:*:*:*:*:*:*:*) carries a wildcard version and an unconfirmed vendor token, so version matching must be done against the vendor/ENISA range (0 < 2.0.3) rather than through CPE lookup alone. The bug class is data exposure rather than code execution or injection, which is why the vector is scored C:L only and there is no integrity or availability component.

Know when Subscriptions For Woocommerce 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 single-request bypass of a broken secret check (AV:N/AC:L/PR:N/UI:N) disclosing aggregate customer PII with no integrity or availability impact, so C:L only.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/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

4
CVSS changed
Sep 17, 2026 - 13:22 NVD
5.3 (MEDIUM)
Patch available
Sep 16, 2026 - 07:01 EUVD
CVE Published
Sep 16, 2026 - 06:00 cve.org
UNKNOWN (no severity yet)
CVE Published
Sep 16, 2026 - 06:00 cve.org
MEDIUM 5.3

DescriptionCVE.org

The Subscriptions for WooCommerce WordPress plugin before 2.0.3 does not correctly validate the shared secret protecting one of its REST endpoints, allowing unauthenticated users to retrieve the store's full list of subscriptions, including customer usernames, product names, recurring amounts and payment dates.

Threat Intelligence Overview

EPSS Score
0.2%
Top 92% exploitable
Prevalence
Medium
popular WooCommerce subscriptions plugin, common on stores but not ubiquitous
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· derived
Poc
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact· derived
Medium

Priority Score

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

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

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