dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2025-30635

HIGH · 8.1 CVSS v3.1 Published 2025-08-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
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
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in ThemeAtelier IDonatePro idonate-pro allows PHP Local File Inclusion.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 confidence

IDonatePro WordPress plugin <= 2.1.9 contains a PHP Local File Inclusion (LFI) vulnerability where the application improperly controls filenames used in include/require statements. Attackers could potentially exploit this to read sensitive local files by manipulating file path parameters.

MitigationUpdate to the latest patched version of IDonatePro. If no patch is available, disable the plugin or implement input validation/WAF rules to restrict file path parameters.

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

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

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
    Check your WordPress site's wp-content/plugins/ directory for the IDonatePro plugin folder, or list installed plugins via WordPress admin under Plugins > Installed Plugins
    Affected if The IDonatePro plugin folder exists in the plugins directory
  2. Check installed IDonatePro version
    Open the plugin's main PHP file or readme.txt and locate the Version header, or check via WordPress admin plugin list
    Affected if The version number is 2.1.9 or lower
  3. Identify vulnerable file inclusion parameter
    Review plugin source code for include/require statements using unsanitized input from request parameters (common targets: 'page', 'file', 'path', 'template', 'load' variables)
    Affected if The plugin contains include/require calls that use $_GET, $_POST, or similar user-supplied parameters without proper validation
  4. Check for active exploitation indicators
    Review web server access logs for suspicious requests to IDonatePro containing directory traversal patterns such as ../, ..\, or absolute paths like /etc/passwd
    Affected if Log entries show LFI exploitation attempts against IDonatePro endpoints

You are affected if IDonatePro plugin version is 2.1.9 or lower AND the vulnerable file inclusion parameter is accessible and not otherwise mitigated.

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

Update to the latest patched version of IDonatePro. If no patch is available, disable the plugin or implement input validation/WAF rules to restrict file path parameters.

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-30635 — 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-30635 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