CVE-2025-30829
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 · uneditedImproper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Arraytics WPCafe wp-cafe allows PHP Local File Inclusion.This issue affects WPCafe: from n/a through <= 2.2.31.
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 confidenceA Local File Inclusion (LFI) vulnerability in the WPCafe WordPress plugin allows attackers to include arbitrary PHP files from the server by manipulating file path parameters in PHP include/require statements. This can lead to remote code execution if an attacker can upload or control included files.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check if WPCafe plugin is installedNavigate to WordPress admin > Plugins > Installed Plugins and look for 'WPCafe' or 'WPCafe - Quick Restaurant Reservation' in the listAffected if WPCafe plugin is present in the plugins list
-
Identify installed WPCafe versionIn the plugins list, look for the version number displayed under the WPCafe plugin name, or check the plugin's main PHP file header for 'Version:' commentAffected if Version is at or below the latest version prior to the patch (version comparison required against fixed release)
-
Verify plugin is activeIn WordPress admin > Plugins, confirm WPCafe shows as 'Active' (not just installed)Affected if Plugin status shows 'Active' - only active instances can be exploited
-
Check for directory traversal in request parametersReview web server access logs for requests containing patterns like '../', '..\', or absolute paths in parameters passed to WPCafe endpoints (typically GET/POST parameters used in include/require logic)Affected if Suspicious traversal patterns found in logs targeting WPCafe URLs
-
Inspect WPCafe includes/requiresIf code access is available, examine WPCafe PHP files for dynamic include/require statements using user-controlled parameters (look for $_GET, $_POST, or similar in include/require paths)Affected if Dynamic file inclusion found using unsanitized input from request parameters
User is affected if WPCafe plugin is installed, active, and running a version that has not been patched for this LFI vulnerability, or if suspicious traversal patterns appear in logs targeting the plugin
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 dataUpdate WPCafe to the latest version immediately. If no patch is available, disable the plugin and implement web application firewall rules to block directory traversal patterns in request parameters.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30829 — 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-30829 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