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

CVE-2026-28060

HIGH · 8.1 CVSS v3.1 Published 2026-03-05
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 ThemeREX S.King stephanie-king allows PHP Local File Inclusion.This issue affects S.King: from n/a through <= 1.5.3.

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

A PHP Local File Inclusion vulnerability exists in the ThemeREX S.King (stephanie-king) WordPress theme due to improper control of filename parameters in include/require statements. An attacker could exploit this to read sensitive files on the server or potentially achieve remote code execution if the server configuration permits remote file inclusion.

MitigationImplement strict input validation on file inclusion paths, use basename() to strip directory traversal sequences, avoid direct use of user input in include/require statements, and update to a patched version if available.

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 ThemeREX S.King theme is installed
    Check your WordPress installation under wp-content/themes/ for a folder named 'stephanie-king' or 's.king' or similar ThemeREX theme directories. List all theme folders to identify if this specific theme is present.
    Affected if The ThemeREX S.King (stephanie-king) theme directory exists in your WordPress themes folder.
  2. Identify the installed theme version
    Open the style.css file within the theme folder and look for the 'Version:' declaration in the file header. This typically appears near the top as 'Version: x.x.x' or check theme.xml if available.
    Affected if The version number found is within the affected range for this CVE (check against any published vulnerable versions).
  3. Locate the vulnerable file inclusion code
    Search within the theme folder for PHP files containing include, require, include_once, or require_once statements that use variable parameters without proper sanitization. Look for patterns like 'include($_GET[...])' or 'require($var)' in files under the theme directory.
    Affected if PHP files contain include/require statements that directly use user-supplied input (GET/POST parameters) without validation or basename() filtering.
  4. Verify the file inclusion endpoint is accessible
    If the vulnerable code is in a PHP file (e.g., in a template or includes folder), attempt to access that file directly via HTTP to confirm it is publicly reachable. Check your web server access logs for requests to the theme's PHP files.
    Affected if The PHP file containing the vulnerable include/require is directly accessible via web request without authentication.
  5. Test for directory traversal capability
    If an include/require statement uses a parameter (e.g., ?file=), attempt a safe test request with a known safe file path like ../../../../../../etc/passwd or ../../wp-config.php to see if the application reflects file contents in the response. Note: Only perform this on authorized systems.
    Affected if The application returns contents of files outside the theme directory when traversal sequences are provided in the parameter.

Your environment is affected if the ThemeREX S.King theme is installed, contains the vulnerable include/require pattern using unsanitized user input, and that endpoint is accessible over the web allowing directory traversal.

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 file inclusion paths, use basename() to strip directory traversal sequences, avoid direct use of user input in include/require statements, and update to a patched version if available.

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-2026-28060 — 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-2026-28060 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