Unauthenticated data disclosure via sensitive debug logging
Published Jan 5, 2024 · Updated Apr 28, 2026
Sensitive information exposure in WP Stripe Checkout 1.2.2.37 and earlier allows remote attackers to read data from a debug log. The plugin's debug-logging path records sensitive information in a log file, but the published advisory does not identify the file, function, logged fields, or request that reaches it. No authentication or user interaction is required; the documented consequence is confidentiality loss only, and the affected logging configuration is undisclosed.
Summary
What happened
Sensitive information exposure in WP Stripe Checkout 1.2.2.37 and earlier allows remote attackers to read data from a debug log. The plugin's debug-logging path records sensitive information in a log file, but the published advisory does not identify the file, function, logged fields, or request that reaches it. No authentication or user interaction is required; the documented consequence is confidentiality loss only, and the affected logging configuration is undisclosed.
The record
- CVE
- CVE-2023-52143
- Published
- Jan 5, 2024
- Updated
- Apr 28, 2026
- Vendor
- NoorsPlugin
- Product
- WP Stripe Checkout
- Classifications
- CWE-532, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 5, 2024CVE publishedPublication date reported by the CVE source.
- Apr 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.2.2.37
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo