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

CVE-2025-67982

HIGH · 8.1 CVSS v3.1 Published 2026-02-20
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 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 · moderate confidence

Local File Inclusion vulnerability in thembay Urna theme allows attackers to include arbitrary local files from the server via unsanitized user input in PHP include/require statements. This can lead to exposure of sensitive configuration files, source code, or potentially remote code execution if the attacker can write files to accessible locations.

MitigationImplement strict input validation on all file inclusion parameters, use allowlists for permitted files, avoid using user input directly in include/require statements, and consider using basename() or realpath() to normalize and validate file paths.

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. Confirm Urna theme is installed
    Check if the /wp-content/themes/urna/ directory exists on the WordPress site. Navigate to Appearance > Themes in WordPress admin to verify the theme is active.
    Affected if The Urna theme by thembay is installed and active.
  2. Identify Urna theme version
    Open the theme's style.css file located at /wp-content/themes/urna/style.css and look for the 'Version:' header in the file comments. Alternatively, check the theme's main PHP file for a version constant.
    Affected if The installed version matches or falls within any known affected version ranges for CVE-2025-67982.
  3. Locate PHP include/require statements with user input
    Search the theme's PHP files for include(), require(), include_once(), or require_once() statements that use variables or parameters without sanitization. Look for patterns like 'include($_GET[...])' or 'require($param)'. Use grep or a code search tool across /wp-content/themes/urna/ directory.
    Affected if Files contain include/require statements that incorporate unsanitized user-supplied input into file paths.
  4. Check for vulnerable file path parameters in AJAX or frontend handlers
    Examine AJAX action handlers (wp_ajax_* and wp_ajax_nopriv_* hooks) and template files that process query parameters. Look for code that reads file paths from $_GET, $_POST, or $_REQUEST and passes them directly to include/require.
    Affected if AJAX handlers or template files accept file path parameters without validation.
  5. Inspect the specific vulnerable code pattern
    Review PHP files that handle template loading or partial file inclusion within the theme. Look for code that appends user-controlled filenames to a base path, such as $base_path . $_GET['file'] or similar constructs, without using basename() or realpath() for validation.
    Affected if The code uses direct string concatenation with user input in file inclusion operations.

A defender is affected if the Urna theme is installed, the vulnerable include/require code pattern exists and is accessible, and the site runs a version within the affected range.

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

Implement strict input validation on all file inclusion parameters, use allowlists for permitted files, avoid using user input directly in include/require statements, and consider using basename() or realpath() to normalize and validate file paths.

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