dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-12362

MEDIUM · 5.3 CVSS v3.1 Published 2025-12-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 myCred – Points Management System For Gamification, Ranks, Badges, and Loyalty Program plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 2.9.7. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to approve withdrawal requests, modify user point balances, and manipulate the payment processing system via the cashcred_pay_now AJAX action.

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 confidence

The myCred plugin for WordPress has a missing authorization vulnerability in the cashcred_pay_now AJAX action (versions up to 2.9.7). The plugin fails to verify user authorization before allowing critical operations, enabling unauthenticated attackers to approve withdrawal requests, modify point balances, and manipulate the payment processing system.

MitigationUpdate to version 2.9.8 or later which should include proper capability checks and nonce verification on the AJAX action. Until then, consider restricting access to the affected AJAX endpoint or disabling the cashcred functionality via web server configuration.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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. Verify myCred plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and locate myCred. Check the version number listed. Alternatively, examine the plugin header in /wp-content/plugins/mycred/plugin.php or use a security scanner to enumerate installed plugins.
    Affected if The installed version is 2.9.7 or earlier (any version up to 2.9.7).
  2. Confirm cashcred addon is active
    In WordPress admin, navigate to myCred > Addons and verify whether the 'cashCred' addon is enabled. The vulnerability only affects environments where this addon is installed and active.
    Affected if The cashcred addon is enabled in the myCred Addons page.
  3. Test AJAX endpoint accessibility
    Send a crafted POST request to /wp-admin/admin-ajax.php with action=cashcred_pay_now and minimal parameters (such as a test payment amount). No authentication token or nonce should be included to test if the endpoint accepts unauthenticated requests.
    Affected if The AJAX endpoint responds without requiring a logged-in session or returns a non-authentication error.
  4. Inspect capability checks in plugin code
    Examine the file handling the cashcred_pay_now AJAX action (typically in /wp-content/plugins/mycred/addons/cashcred/inc/ or similar). Look for current_user_can() or wp_verify_nonce() calls at the start of the handler function.
    Affected if No capability check (current_user_can) or nonce verification (wp_verify_nonce) is found at the beginning of the cashcred_pay_now handler.

You are affected if myCred version is 2.9.7 or earlier AND the cashcred addon is enabled AND the AJAX endpoint accepts unauthenticated requests without proper capability or nonce validation.

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 version 2.9.8 or later which should include proper capability checks and nonce verification on the AJAX action. Until then, consider restricting access to the affected AJAX endpoint or disabling the cashcred functionality via web server configuration.

Recommended fix Moderate confidence

Latest version of myCred plugin (version 2.9.8 or higher)

  1. Check the WordPress admin dashboard for plugin updates under Plugins > All Plugins
  2. Update myCred plugin to the latest available version
  3. After updating, verify the cashcred_pay_now AJAX action requires authentication
  4. Confirm unauthenticated users can no longer access withdrawal approval, point balance modifications, or payment processing functions

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12362 — 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-12362 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