Coupon Referral ProgramWordPress extension · Wpswings
CVE-2023-52190
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 WP Swings Coupon Referral Program.This issue affects Coupon Referral Program: from n/a through 1.7.2.
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 Swings Coupon Referral Program WordPress plugin (versions through 1.7.2) contains an information disclosure vulnerability allowing unauthorized actors to access sensitive data. The CVSS 7.5 score indicates a high-severity network-exploitable issue without authentication requirements.
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
Coupon Referral ProgramWordPress extension
<= 1.7.2CVSS 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.
-
Verify WP Swings Coupon Referral Program plugin is installedCheck the WordPress plugins directory (wp-content/plugins) for a folder named 'woo-refund-and-exchange' or search for 'WP Swings' or 'Coupon Referral Program' in the plugin filesAffected if The plugin folder exists on the server
-
Identify the installed plugin versionOpen the main plugin file (typically plugin-name.php) and look for the version header in the plugin comment block, or check the WordPress admin under Plugins > Installed PluginsAffected if The version displayed is 1.7.2 or any lower version number
-
Confirm the version falls within the affected rangeCompare the installed version number to the affected range: any version 1.7.2 or below is vulnerableAffected if Installed version is 1.7.2 or lower (for example: 1.7.2, 1.7.1, 1.6.0, 1.0.0)
-
Verify the plugin is activeCheck WordPress admin > Plugins > Installed Plugins, or query the wp_options table for option_name = 'active_plugins'Affected if The plugin shows as 'Active' in WordPress or appears in the active_plugins array
You are affected if the WP Swings Coupon Referral Program plugin is installed with version 1.7.2 or any earlier version and the plugin is active on your WordPress site.
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 the plugin when a patch is released. Until then, restrict plugin access via firewall rules or disable the plugin if the risk is unacceptable.
Fix this in Coupon Referral Program
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-52190 — 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-52190 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