dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-15260

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
The MyRewards – Loyalty Points and Rewards for WooCommerce plugin for WordPress is vulnerable to missing authorization in all versions up to, and including, 5.6.1. This is due to the plugin not properly verifying that a user is authorized to perform an action in the 'ajax' function. This makes it possible for authenticated attackers, with subscriber level access and above, to modify, add, or delete loyalty program earning rules, including manipulating point multipliers to arbitrary values.

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 · high confidence

The MyRewards WordPress plugin fails to perform capability checks in its AJAX handlers, allowing any authenticated user with subscriber-level access to modify, add, or delete loyalty program earning rules and manipulate point multipliers. This is a classic broken access control vulnerability where the 'ajax' function trusts user input without verifying authorization.

MitigationUpdate to plugin version 5.6.2 or later which implements proper authorization checks. If immediate update is not feasible, disable the plugin or restrict AJAX endpoint access at the web server level.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm MyRewards plugin is installed
    Navigate to WordPress admin dashboard under Plugins > Installed Plugins, or inspect the wp-content/plugins/ directory for a folder named 'myrewards' or similar.
    Affected if The plugin is present and active in the WordPress installation.
  2. Identify the installed version
    In WordPress admin, find the MyRewards plugin entry and read the version number displayed. Alternatively, open the main plugin PHP file (e.g., myrewards.php) and locate the Version header in the plugin comments.
    Affected if The version is lower than 5.6.2 (the patched version).
  3. Verify AJAX functionality is enabled
    Check if the WordPress AJAX endpoint /wp-admin/admin-ajax.php is accessible and the plugin registers AJAX action hooks. Inspect the plugin code for add_action('wp_ajax_', ...) calls.
    Affected if The plugin exposes AJAX handlers and admin-ajax.php is accessible.
  4. Confirm presence of subscriber-level user accounts
    In WordPress admin, go to Users > All Users and check if any users have the Subscriber role, or query the wp_usermeta table for users with wp_capability = a:1:{s:10:"subscriber";b:1;}.
    Affected if There exists at least one user with Subscriber role.
  5. Test AJAX endpoint accessibility with low-privilege credentials
    Send a crafted AJAX request (e.g., via curl or Burp) to admin-ajax.php with a nonce and action parameter used by MyRewards (check plugin for action names like 'myrewards_save_rule'), authenticated as a subscriber-level user.
    Affected if The request succeeds and modifies earning rules or point multipliers without returning a 403 or capability error.

A user is affected if the MyRewards plugin is installed with a version lower than 5.6.2, the AJAX functionality is exposed, and at least one subscriber-level user account exists in the WordPress installation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to plugin version 5.6.2 or later which implements proper authorization checks. If immediate update is not feasible, disable the plugin or restrict AJAX endpoint access at the web server level.

Recommended fix High confidence

Version 5.6.2 or later of MyRewards – Loyalty Points and Rewards for WooCommerce plugin

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'MyRewards – Loyalty Points and Rewards for WooCommerce' plugin
  4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. Alternatively, navigate to Plugins > Add New > Upload Plugin to manually upload version 5.6.2 or later if automatic update is not available
  6. After updating, verify the version number reflects 5.6.2 or higher under the plugin list

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-15260 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-15260 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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