dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-60045

HIGH · 7.5 CVSS v3.1 Published 2025-12-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 ThemeAtelier IDonatePro idonate-pro allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects IDonatePro: from n/a through <= 2.1.11.

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

Missing Authorization (IDOR/Broken Access Control) vulnerability in the IDonatePro WordPress plugin allows unauthenticated or unauthorized users to access functionality that should be restricted by Access Control Lists (ACLs). This could permit viewing or modifying donation data, campaign settings, or other sensitive administrative functions without proper privileges.

MitigationImplement proper authorization checks (capability checks and nonce verification) on all sensitive functions and AJAX endpoints within the plugin. Restrict access to administrative functionality to authenticated users with appropriate roles and capabilities.

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 IDonatePro plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'IDonatePro' or 'iDonate Pro' in the list of active plugins.
    Affected if The plugin is installed and active, making the vulnerability potentially applicable to this WordPress site.
  2. Identify installed plugin version
    In the Plugins list, click on the plugin name or view the plugin files. Open the main plugin file (usually idonate-pro.php or similar) and look for the version defined in the plugin header comment (e.g., 'Version: 1.2.3').
    Affected if The installed version matches or falls within the affected version range for CVE-2025-60045 (check against NVD or WordPress plugin repository for specific vulnerable versions).
  3. Check for unauthenticated AJAX endpoints
    Inspect the plugin directory (typically /wp-content/plugins/IDonatePro/) for PHP files containing 'add_action("wp_ajax_' or 'add_action("wp_ajax_nopriv_' hooks. Examine if these endpoints perform sensitive operations without capability checks.
    Affected if AJAX endpoints exist that handle donation data, campaign settings, or administrative functions without requiring authentication or proper capability verification.
  4. Inspect Access Control List (ACL) implementation
    Search plugin files for ACL-related functions, capability checks (current_user_can, check_admin_referer, wp_verify_nonce), or role definitions. Look in files related to donation management, campaign settings, or user access.
    Affected if No capability checks (current_user_can) or nonce verification (wp_verify_nonce, check_admin_referer) are found before executing sensitive operations on donation data or admin functions.
  5. Test for IDOR vulnerability on donation data
    Using a browser or HTTP tool, attempt to access or modify donation records, campaign configurations, or user data without logging in or with a low-privilege account. Check if the application returns sensitive data or allows unauthorized modifications.
    Affected if Unauthenticated or unauthorized requests successfully retrieve or modify donation data, campaign settings, or administrative functions that should require proper authorization.

A site is affected if it runs a version of IDonatePro within the vulnerable version range AND exhibits missing authorization checks on sensitive AJAX endpoints or functions handling donation/administrative data.

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 (capability checks and nonce verification) on all sensitive functions and AJAX endpoints within the plugin. Restrict access to administrative functionality to authenticated users with appropriate roles and capabilities.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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