CVE-2026-28129
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 · uneditedImproper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in axiomthemes Little Birdies little-birdies allows PHP Local File Inclusion.This issue affects Little Birdies: from n/a through <= 1.3.16.
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 confidenceLocal File Inclusion vulnerability in the Little Birdies WordPress theme allows attackers to include arbitrary PHP files from the server through improper control of filename parameters in include/require statements.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Little Birdies theme installationIn WordPress admin, go to Appearance > Themes to verify the Little Birdies theme is active. Note the theme version displayed there, or check the style.css file in wp-content/themes/little-birdies/ for the 'Version:' header.Affected if The Little Birdies theme is installed and active, and the version is within the affected range (if known) or unpatched.
-
Locate vulnerable include/require statementsSearch theme PHP files for include, include_once, require, or require_once statements that use variables in the path without sanitization. Check files in the theme root and any subdirectories, particularly in functions.php, header.php, or custom template files.Affected if Files contain include/require statements using unsanitized variables like include($file) or require($_GET['page']) without validation.
-
Inspect the vulnerable parameter entry pointIdentify which PHP file handles the file inclusion parameter. Common patterns include ?file=, ?page=, ?template=, or ?path= in URLs. Test if the parameter accepts arbitrary file paths (e.g., ../../../../wp-config.php).Affected if The parameter can be manipulated to traverse directories and point to arbitrary PHP files on the server.
-
Verify allow_url_include and PHP configurationCheck phpinfo() or the site's PHP configuration for allow_url_include setting. While this is LFI (local), the impact is worse if allow_url_include is On.Affected if allow_url_include is enabled (this amplifies impact but is not required for LFI to work).
A user is affected if the Little Birdies WordPress theme is installed with an unpatched version and contains the vulnerable file inclusion code accessible via web request.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate to a patched version of the Little Birdies theme; if unavailable, audit and fix vulnerable include/require statements to use whitelist validation or remove the functionality entirely.
- Consultation2.0 h
- Implementation4.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,320.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28129 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-28129 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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