LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24581: WordPress Points and Rewards for WooCommerce plugin <= 2.9.5 - Broken Access Control vulnerability

Missing Authorization vulnerability in WP Swings Points and Rewards for WooCommerce points-and-rewards-for-woocommerce allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Points and Rewards for WooCommerce: from n/a through <= 2.9.5.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-24581 affects the WordPress Points and Rewards for WooCommerce plugin through version 2.9.5. It is a broken access control issue: a logged-in user may perform actions they should not be authorized to perform. Public sources rate it medium severity. No source provided indicates active exploitation.

Executive priority

Treat as a moderate-priority WordPress risk. Prioritize sites that allow customer registration or have high-value reward balances. It is not currently supported as actively exploited by the provided sources, but affected public WooCommerce sites should be reviewed and updated when vendor guidance is available.

Technical view

The CVE describes CWE-862 Missing Authorization in WP Swings Points and Rewards for WooCommerce <=2.9.5. CVSS 3.1 is 5.4: network-accessible, low complexity, low privileges required, no user interaction, with low integrity and availability impact and no confidentiality impact.

Likely exposure

Exposure is limited to WordPress/WooCommerce sites running the Points and Rewards for WooCommerce plugin at version 2.9.5 or earlier. The CVSS vector indicates exploitation requires an authenticated low-privilege user account.

Exploitation context

The provided sources do not include exploit code, public exploitation claims, or CISA KEV listing. The issue is still relevant because many WordPress sites allow customer accounts, which may satisfy the low-privilege requirement.

Researcher notes

Public detail is limited. The source bundle identifies the vulnerability class, affected version range, CVSS vector, and Patchstack entry, but does not provide endpoint-level details, a proof of concept, active exploitation evidence, or a named fixed version.

Mitigation direction

  • Inventory WordPress sites for the points-and-rewards-for-woocommerce plugin.
  • Identify installations running version 2.9.5 or earlier.
  • Check WP Swings and Patchstack guidance for a fixed release or official workaround.
  • Upgrade when an official fixed version is available.
  • Temporarily disable the plugin if exposure is unacceptable.
  • Restrict account creation and plugin-related privileges to trusted users where feasible.

Validation and detection

  • Confirm plugin name and version from WordPress administration or asset inventory.
  • Review whether public customer registration is enabled on affected sites.
  • Check logs for unusual rewards, points, or plugin-setting changes.
  • Verify remediation by confirming the plugin is no longer at an affected version.
  • Document any compensating controls if the plugin cannot be updated.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-24581 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2026-24581Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
WP SwingsPoints and Rewards for WooCommercepoints-and-rewards-for-woocommerce, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.