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

CVE-2026-28062

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 Happy Baby happy-baby allows PHP Local File Inclusion.This issue affects Happy Baby: from n/a through <= 1.2.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

A PHP Local File Inclusion vulnerability exists in the ThemeREX Happy Baby WordPress theme (versions up to 1.2.12). The vulnerability allows remote attackers to include and execute arbitrary PHP files from the server through improper validation of file paths in include/require statements, potentially leading to complete system compromise.

MitigationUpdate Happy Baby theme to a patched version if available; if no patch exists, replace the theme with a supported alternative or implement a WAF rule to block directory traversal patterns in URL parameters.

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 the Happy Baby theme directory
    Check the wp-content/themes/ directory for a folder named 'happy-baby', 'trx_happy_baby', or similar ThemeREX Happy Baby theme folder. Common paths include /wp-content/themes/happy-baby/ or /wp-content/themes/trx_happy_baby/.
    Affected if The theme folder exists in the WordPress themes directory.
  2. Identify the installed theme version
    Open the style.css file in the identified theme folder and locate the 'Version:' header in the theme comments at the top of the file. Alternatively, check version.php if present in the theme folder.
    Affected if The version number listed is 1.2.12 or lower, indicating the theme is within the affected range.
  3. Verify the theme is active
    In the WordPress admin dashboard, navigate to Appearance > Themes to confirm whether the Happy Baby theme is currently activated. Alternatively, check the wp_options database table for the 'template' or 'stylesheet' option values matching the theme folder name.
    Affected if The Happy Baby theme is activated and serving pages on the site.
  4. Search for vulnerable include/require patterns
    Use grep or a file search to scan PHP files within the theme folder for include, require, include_once, or require_once statements that use variables in the file path without proper sanitization. Look for patterns like 'include($', 'require($', 'include $_GET', 'require $_POST' without validation functions.
    Affected if PHP files in the theme contain include/require statements that incorporate user-controlled input without validation or path traversal protection.
  5. Test for directory traversal in URL parameters
    If the theme is active and vulnerable code is suspected, examine HTTP requests for parameters that might control file includes. Common vulnerable parameter names include 'file', 'path', 'page', 'template', 'theme', 'style', or similar. Attempt a controlled test request with a pattern like '?param=../../../../etc/passwd' (or a benign test file) to observe if the application attempts to include arbitrary files.
    Affected if The application returns file contents from outside the intended theme directory, confirming the LFI vulnerability is exploitable.

If the Happy Baby theme version is 1.2.12 or lower, the theme is activated, and vulnerable include/require patterns exist in the theme files, the environment is affected by this CVE.

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

Update Happy Baby theme to a patched version if available; if no patch exists, replace the theme with a supported alternative or implement a WAF rule to block directory traversal patterns in URL parameters.

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