Stripe Payment GatewayWordPress extension · Woocommerce
CVE-2023-35049
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMissing Authorization vulnerability in WooCommerce WooCommerce Stripe Payment Gateway.This issue affects WooCommerce Stripe Payment Gateway: from n/a through 7.4.0.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceMissing Authorization vulnerability in the WooCommerce Stripe Payment Gateway plugin allows unauthenticated or unauthorized users to access sensitive functions or data due to insufficient capability checks or authentication validation. This critical flaw affects versions through 7.4.0 and could enable attackers to manipulate payments, access administrative functions, or exfiltrate data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Stripe Payment GatewayWordPress extension
< 7.4.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify WooCommerce Stripe Payment Gateway is installedNavigate to WordPress admin > Plugins, locate WooCommerce Stripe Payment Gateway in the list of installed plugins and confirm it is activeAffected if The plugin is installed and active in WordPress
-
Check installed version against affected rangeIn WordPress admin > Plugins, find the WooCommerce Stripe Payment Gateway entry and read the version number displayed under the plugin nameAffected if The version number is lower than 7.4.1 (any version through 7.4.0 is affected)
-
Inspect admin user accounts for unauthorized creationIn WordPress admin > Users, review all administrator-level accounts for any that were created recently or are unfamiliar; check user registration dates and capabilitiesAffected if Unknown admin accounts exist that were not created by legitimate administrators
-
Examine Stripe payment settings for tamperingNavigate to WooCommerce > Settings > Payments > Stripe and verify that the Stripe API keys, webhook URL, and payment settings match your known configuration; check for any unexpected changesAffected if API credentials have been changed or settings differ from your documented configuration
The environment is affected if the WooCommerce Stripe Payment Gateway plugin is installed with a version lower than 7.4.1, as the missing authorization vulnerability allows unauthenticated access to sensitive functions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped7.4.1
Update WooCommerce Stripe Payment Gateway to the latest version (beyond 7.4.0) which includes proper authorization checks and capability validation. Verify the update does not introduce regressions in payment processing.
Version 7.4.1 or later
- Update the WooCommerce Stripe Payment Gateway plugin to version 7.4.1 or later via the WordPress admin dashboard Plugins section, or reinstall the plugin from the WordPress plugin repository.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Stripe Payment Gateway
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35049 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-35049 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data