Wp Stripe CheckoutWordPress extension · Noorsplugin
CVE-2023-52143
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 · uneditedExposure of Sensitive Information to an Unauthorized Actor vulnerability in Naa986 WP Stripe Checkout.This issue affects WP Stripe Checkout: from n/a through 1.2.2.37.
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 · moderate confidenceThe WP Stripe Checkout plugin versions up to 1.2.2.37 contain an information disclosure vulnerability allowing unauthenticated actors to access sensitive data. Given this is a Stripe payment plugin, the exposed data likely includes payment-related information, API credentials, or customer transaction details accessible through an unprotected endpoint or functionality.
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
Wp Stripe CheckoutWordPress extension
<= 1.2.2.37CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
-
Confirm WP Stripe Checkout plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'WP Stripe Checkout' by Noorsplugin. Alternatively, check the wp-content/plugins directory for a folder named 'wp-stripe-checkout' or similar.Affected if The plugin is present in the WordPress installation
-
Identify installed plugin versionIn WordPress admin > Plugins, find WP Stripe Checkout and read the version number displayed beneath the plugin name. Alternatively, open the main plugin PHP file (usually wp-stripe-checkout.php) and look for the 'Version' header in the plugin comments.Affected if Version is 1.2.2.37 or lower
-
Locate the plugin directory structureNavigate to wp-content/plugins/ in the WordPress installation and identify the WP Stripe Checkout plugin folder. Note all PHP files and subdirectories present.Affected if Plugin files exist in the WordPress plugins directory at versions <= 1.2.2.37
-
Identify exposed endpoints or AJAX actionsReview plugin PHP files for registered REST API routes, AJAX actions, or wp-admin admin-ajax.php callbacks. Search for add_action calls with 'wp_ajax' or 'wp_ajax_nopriv' prefixes that may be accessible without authentication.Affected if Unauthenticated-accessible AJAX actions or REST endpoints are registered in the plugin
-
Check for unprotected data access pointsExamine the plugin for PHP files that handle data retrieval or display without checking user authentication (check for missing is_user_logged_in() or current_user_can() calls). Look for any files that output sensitive data like customer details, transaction records, or API configurations.Affected if Plugin contains endpoints or files accessible without authentication that expose sensitive data
If WP Stripe Checkout version 1.2.2.37 or lower is installed and contains unauthenticated-accessible endpoints or data exposure functionality, the environment is affected by CVE-2023-52143.
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.
From vendor dataUpdate to the latest version of WP Stripe Checkout once available, or implement web application firewall rules to restrict unauthenticated access to plugin endpoints. Audit logs and access patterns should be reviewed for indicators of compromise.
Fix this in Wp Stripe Checkout
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-52143 — 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-52143 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