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

CVE-2026-28092

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 Sounder sounder allows PHP Local File Inclusion.This issue affects Sounder: from n/a through <= 1.3.11.

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

PHP Local File Inclusion vulnerability in ThemeREX Sounder plugin allows attackers to include arbitrary local PHP files due to improper validation of include/require statement parameters, potentially leading to remote code execution.

MitigationImplement strict input validation and sanitization on file inclusion parameters, using whitelist-based approaches and restricting file paths to expected directories to prevent arbitrary file inclusion.

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. Locate ThemeREX Sounder plugin files
    Search the web server document root for the 'trx_sounder' or 'sounder' directory, typically under wp-content/plugins/ for WordPress or in the themes/plugins folder for the respective CMS.
    Affected if The plugin directory exists on the server.
  2. Identify the installed plugin version
    Open the main plugin PHP file (usually named index.php, main.php, or trx_sounder.php) and look for a version constant or comment at the top of the file.
    Affected if The version cannot be determined or is unknown, treat as potentially vulnerable.
  3. Verify the file inclusion vulnerability is present
    Search the plugin PHP files for include, require, include_once, or require_once statements that use variables directly in the path (e.g., include($file), require($_GET['file'])) without proper sanitization.
    Affected if Unsanitized file inclusion calls are found that accept user-controlled input.
  4. Check if the vulnerable endpoint is accessible
    Identify PHP scripts that handle the file inclusion and determine if they are accessible via HTTP requests without authentication or with standard user privileges.
    Affected if The vulnerable script is reachable over the network.
  5. Confirm the plugin processes file path parameters
    Review the code flow from HTTP request parameters (GET/POST) to the include/require statement to confirm user input reaches the file inclusion function without validation.
    Affected if User-supplied parameters flow directly to include/require without sanitization.

A user is affected if the ThemeREX Sounder plugin is installed and its code contains unsanitized file inclusion logic that accepts user input and is accessible via web requests.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and sanitization on file inclusion parameters, using whitelist-based approaches and restricting file paths to expected directories to prevent arbitrary file inclusion.

Recommended fix Moderate confidence

Update to the latest version of ThemeREX Sounder once a patched release is available from the vendor (check WordPress plugin repository or ThemeREX directly)

  1. Check the ThemeREX Sounder plugin currently installed on your WordPress site
  2. Review the plugin's changelog or the WordPress plugin repository for any security updates beyond version 1.3.11
  3. If no update is available from the vendor, consider uninstalling and removing the ThemeREX Sounder plugin until a patched version is released
  4. If the plugin is required, monitor plugin security advisories and WordPress plugin repository for updated versions
  5. Implement WAF (Web Application Firewall) rules to help detect and block LFI attempts targeting the vulnerable parameter

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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