Points And Rewards For WoocommerceWordPress extension · Wpswings
CVE-2023-27608
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 WP Swings Points and Rewards for WooCommerce.This issue affects Points and Rewards for WooCommerce: from n/a through 1.5.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 · moderate confidenceA missing authorization vulnerability in the WP Swings Points and Rewards for WooCommerce plugin allows unauthenticated or unauthorized users to access functionality they should not have permission to use, potentially leading to unauthorized manipulation of points and rewards 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
Points And Rewards For WoocommerceWordPress extension
<= 1.5.0CVSS 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 plugin installation and activation statusLog into the WordPress admin dashboard, navigate to Plugins > Installed Plugins, and locate 'Points and Rewards for WooCommerce' by WP Swings. Confirm whether it is installed and currently activated.Affected if The plugin is installed and activated on the WooCommerce site.
-
Identify installed plugin versionIn the WordPress admin under Plugins > Installed Plugins, click on the plugin name to view its details, or check the plugin folder for a readme.txt or main PHP file that contains a 'Version:' header. Alternatively, access the site via FTP or file manager and read the main plugin file (typically points-and-rewards-for-woocommerce.php) to find the version number.Affected if The installed version is 1.5.0 or any earlier version (1.0.x through 1.5.0).
-
Check for active WooCommerce installationVerify that WooCommerce is installed and active on the same WordPress site, as this plugin extends WooCommerce functionality. Navigate to Plugins > Installed Plugins and confirm WooCommerce is activated.Affected if WooCommerce is active and the vulnerable plugin version is in the affected range.
-
Audit user access controls on points/rewards endpointsReview the site's access logs or use a security plugin to test whether unauthenticated requests to points-related AJAX actions (commonly found in /wp-admin/admin-ajax.php with 'wps_' or 'points_' prefixes) are being processed without capability checks. Use a tool like Burp Suite or curl to send unauthenticated POST requests to common plugin action endpoints and observe if they execute without a 403 or login redirect.Affected if The plugin processes requests from unauthenticated or unauthorized users without verifying their capabilities or authentication status.
The environment is affected if the Points and Rewards for WooCommerce plugin version 1.5.0 or lower is installed and active on a WooCommerce site, particularly if unauthenticated users can manipulate points data.
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 the Points and Rewards for WooCommerce plugin to a version beyond 1.5.0 once available, or implement proper authorization checks (checking user capabilities/permissions) on all sensitive plugin functions.
Fix this in Points And Rewards For Woocommerce
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-27608 — 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-27608 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