CVE-2025-54689
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 thembay Urna urna allows PHP Local File Inclusion.This issue affects Urna: from n/a through <= 2.5.7.
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 · high confidenceA PHP Local File Inclusion (LFI) vulnerability in thembay Urna allows attackers to include arbitrary files on the server through improper input validation in include/require statements. This can lead to sensitive file disclosure and potentially remote code execution.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Urna theme installationCheck your WordPress installation for the Urna theme by examining the themes directory (wp-content/themes/urna) or via WordPress admin theme listAffected if The Urna theme is present in the WordPress installation
-
Identify Urna versionLocate the version information in the Urna theme directory - check style.css header, version.php, or theme.json metadataAffected if The installed version cannot be determined or is older than the patched version
-
Locate file inclusion codeSearch Urna PHP files for include(), require(), include_once(), or require_once() statements that accept parameters directly from $_GET, $_POST, or $_REQUEST without sanitizationAffected if Unsanitized user input reaches file inclusion functions in accessible PHP files
-
Check PHP allow_url_include settingReview php.ini configuration or execute phpinfo() to check the allow_url_include directiveAffected if allow_url_include is enabled (On), which would allow remote file inclusion in addition to local
-
Test accessible file inclusion parametersIdentify URL parameters passed to the vulnerable include/require paths and test with benign file paths (e.g., ../../../../etc/passwd) to confirm LFI behaviorAffected if Arbitrary local files can be included and their contents disclosed via HTTP requests
You are affected if the Urna theme is installed and contains file inclusion code that uses unsanitized user-supplied input, with the vulnerable endpoints accessible via web requests.
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 Urna to the latest patched version. If no patch is available, implement strict input validation with whitelist filtering on file inclusion parameters and ensure allow_url_include is disabled in PHP configuration.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54689 — 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-54689 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