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

CVE-2025-67528

HIGH · 7.5 CVSS v3.1 Published 2025-12-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable 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 thembay Urna urna allows PHP Local File Inclusion.This issue affects Urna: from n/a through <= 2.5.12.

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 confidence

Local File Inclusion (LFI) vulnerability in thembay Urna theme allows attackers to manipulate filename parameters in PHP include/require statements to read arbitrary local files from the server. This occurs due to improper input validation, potentially exposing sensitive configuration files, source code, or system files.

MitigationUpgrade Urna theme to the latest version (>2.5.12) which contains the patch, or implement strict input validation/whitelisting on file inclusion parameters to prevent path traversal attacks.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Urna theme is installed
    Check for the presence of the 'urna' directory in your WordPress themes folder: inspect the path /wp-content/themes/urna/ via FTP, file manager, or the WordPress theme administration interface.
    Affected if The thembay Urna theme directory exists in the WordPress installation.
  2. Identify the installed version of Urna theme
    Locate the theme version number in the theme's style.css file (usually at /wp-content/themes/urna/style.css) or in the theme's functions.php file, then compare it to the affected version range.
    Affected if The installed version is 2.5.12 or earlier (any version below the patched release).
  3. Inspect theme files for file inclusion functions
    Search theme PHP files (particularly in /wp-content/themes/urna/ and subdirectories) for include, require, include_once, or require_once statements that use dynamic variables or parameters without proper sanitization, such as: include($file); or require($_GET['file']);
    Affected if Theme files contain dynamic file inclusion statements that accept user-controlled input without validation.
  4. Review file parameter handling in theme templates
    Examine theme template files that handle filename, file, path, or template parameters (commonly in header, footer, or layout files) to determine if these parameters are used in include/require statements without sanitization.
    Affected if The theme accepts filename parameters via GET/POST requests and uses them directly in PHP inclusion functions.
  5. Test for LFI vulnerability safely
    If you have access to a staging environment, attempt to include a known file (e.g., reading a non-sensitive configuration file) through suspected vulnerable parameters to confirm the vulnerability exists. Only do this in non-production environments.
    Affected if The application successfully reads arbitrary local files when filename parameters are manipulated (e.g., ../../../wp-config.php).

You are affected if the Urna theme version is 2.5.12 or earlier and your theme files contain dynamic file inclusion logic that processes user input without validation.

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

Upgrade Urna theme to the latest version (>2.5.12) which contains the patch, or implement strict input validation/whitelisting on file inclusion parameters to prevent path traversal attacks.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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 locally
dbcve dependency scanner

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