dbcve.org
IdonateWordPress extension · Themeatelier

CVE-2025-67583

MEDIUM · 5.3 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to 2.1.16 or later.
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
Missing Authorization vulnerability in Foysal Imran IDonate idonate allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects IDonate: from n/a through <= 2.1.15.

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 vulnerability in IDonate allows attackers to exploit incorrectly configured access control security levels, potentially gaining unauthorized access to functionality or data that should be restricted based on user privileges.

MitigationImplement proper authorization checks across all sensitive endpoints and functions, ensuring role-based access control (RBAC) is correctly enforced and security levels are properly configured.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
IdonateWordPress extension
Affected:< 2.1.16

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. Check installed Idonate theme version
    Locate the theme's style.css file in wp-content/themes/idonate/ and read the Version header, or check the version in WordPress Admin under Appearance > Themes
    Affected if The version listed is below 2.1.16 (e.g., 2.1.15, 2.0.x, 1.x)
  2. Identify sensitive admin endpoints or functions
    Review the theme's PHP files in the includes/ or classes/ directories for functions handling user data, donations, or admin actions
    Affected if Endpoints that modify data or access sensitive information do not include capability checks (like current_user_can()) or role verification
  3. Test access to restricted functionality
    Attempt to access donation management, user data export, or settings pages while logged out or as a low-privilege user (e.g., subscriber)
    Affected if The application returns sensitive data or allows privileged actions without requiring authentication or proper role validation
  4. Review role-based access control configuration
    Examine the theme's code for security level assignments (e.g., access, user_level, or capability parameters) and compare against WordPress user roles
    Affected if Security levels are set to a value that grants access to unprivileged users, or no role check is performed before executing sensitive operations

A user is affected if their Idonate theme version is below 2.1.16 AND sensitive endpoints or functions can be accessed or executed 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.

dbcve · scoped
Upgrade available Upgrade to 2.1.16 or later
Fixed in 2.1.16
Interim mitigation

Implement proper authorization checks across all sensitive endpoints and functions, ensuring role-based access control (RBAC) is correctly enforced and security levels are properly configured.

Recommended fix High confidence

2.1.16

  1. 1. Backup your WordPress site database and files before making any changes
  2. 2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  3. 3. Find the IDonate plugin in the plugin list
  4. 4. If an update is available, click 'Update Now' to update IDonate to version 2.1.16
  5. 5. Alternatively, download IDonate version 2.1.16 from a trusted source and upload it via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the installed version shows 2.1.16 or higher
  7. 7. Test that the authorization controls are functioning correctly

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

Fix this in Idonate Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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