dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-48147

MEDIUM · 6.5 CVSS v3.1 Published 2025-06-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/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
Missing Authorization vulnerability in Crypto Cloud CryptoCloud - Crypto Payment Gateway cryptocloud-crypto-payment-gateway allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects CryptoCloud - Crypto Payment Gateway: from n/a through <= 2.1.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 confidence

This is a missing authorization vulnerability in the CryptoCloud WordPress payment gateway plugin. The plugin fails to properly enforce access control checks on certain functions or endpoints, allowing authenticated or unauthenticated attackers to access sensitive functionality or data that should be restricted to authorized users. The vulnerability stems from incorrectly configured access control security levels in versions up to and including 2.1.2.

MitigationImplement proper authorization checks on all sensitive endpoints and functions within the plugin, ensuring that each action verifies the user's permissions before execution. Update to a patched version if available from the vendor, or disable the plugin until a fix can be applied.

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
Low

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

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. Locate CryptoCloud plugin version
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, find 'CryptoCloud' or 'CryptoCloud Payment Gateway' in the list. The version number is displayed below the plugin name. Alternatively, inspect the plugin main file header or readme.txt file in /wp-content/plugins/
    Affected if Version listed is 2.1.2 or lower, or no version is displayed but the plugin name matches CryptoCloud payment gateway
  2. Confirm plugin is active
    In WordPress admin under Plugins > Installed Plugins, verify the CryptoCloud plugin shows as 'Active' (the plugin must be active for the vulnerability to be exploitable)
    Affected if Plugin status shows as Active
  3. Check for publicly accessible admin functions
    Review the plugin directory /wp-content/plugins/ for PHP files containing function definitions related to settings, orders, or payment processing. Test accessing these function URLs directly via browser or curl without authentication to see if they respond without requiring login credentials
    Affected if Any sensitive plugin functions or AJAX endpoints respond without requiring WordPress user authentication or capability checks
  4. Inspect plugin capability configuration
    Examine the main plugin PHP files for function declarations (add_action, add_filter) and check if admin hooks include current_user_can() or similar authorization checks. Look for 'init', 'wp_ajax_', or 'admin_post_' hooks without permission_callback parameters
    Affected if Hooks that should require authorization (such as saving settings, processing orders, or modifying plugin configuration) lack current_user_can() verification or permission_callback parameters

The environment is affected if the CryptoCloud plugin version is 2.1.2 or lower and the plugin is active, with sensitive functions or endpoints accessible without proper authorization checks.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authorization checks on all sensitive endpoints and functions within the plugin, ensuring that each action verifies the user's permissions before execution. Update to a patched version if available from the vendor, or disable the plugin until a fix can be applied.

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

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 locally
dbcve dependency scanner

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