CVE-2025-58938
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 · uneditedMissing Authorization vulnerability in ThemeAtelier IDonatePro idonate-pro allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects IDonatePro: from n/a through <= 2.1.9.
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 confidenceThis is a missing authorization vulnerability in the IDonatePro WordPress plugin (versions up to 2.1.9). The plugin fails to properly enforce access control checks on certain functionality, allowing attackers to exploit incorrectly configured security levels. This could permit unauthorized users to access or manipulate donation-related features and data that should require proper authentication and authorization.
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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify IDonatePro plugin installation and versionIn WordPress admin, go to Plugins > Installed Plugins and locate IDonatePro. Note the version number displayed. Alternatively, check the plugin main file header via file system.Affected if The installed version is 2.1.9 or lower (any version up to and including 2.1.9).
-
Inspect plugin AJAX endpoints for capability checksReview the plugin PHP files for AJAX action handlers (wp_ajax_ and wp_ajax_nopriv_ hooks). Look for functions handling donation data, campaign settings, or user data. Check if these handlers call current_user_can() or a similar capability check before processing requests.Affected if Any AJAX endpoint handling sensitive donation operations lacks a current_user_can() or equivalent permission check, or only checks for a logged-in user without verifying specific capabilities.
-
Review donation management functions for authorizationExamine PHP functions related to creating, updating, deleting, or viewing donations, campaigns, or donor records. Search the plugin code for function definitions handling these operations and verify they include role or capability validation.Affected if Functions that access or modify donation data do not verify user roles or capabilities before executing.
-
Check admin page access controlsIdentify plugin admin menu pages and their associated handler functions. Verify that each page load or form submission validates that the current user has appropriate administrative privileges.Affected if Admin pages or forms for managing donations or plugin settings are accessible to users without administrator or appropriate roles.
You are affected if IDonatePro version 2.1.9 or lower is installed AND the plugin contains AJAX endpoints or functions handling donation data that lack proper capability checks or role-based access validation.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement proper capability checks, nonce verification, and role-based access control (RBAC) on all sensitive functions and AJAX endpoints within the plugin. Validate user permissions before allowing any data access or modification operations.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58938 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-58938 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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