CVE-2026-22428
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 AncoraThemes Tooth Fairy tooth-fairy allows PHP Local File Inclusion.This issue affects Tooth Fairy: from n/a through <= 1.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 confidenceA Local File Inclusion (LFI) vulnerability in the Tooth Fairy WordPress plugin by AncoraThemes allows unauthenticated attackers to include arbitrary local files from the server via improper validation of file paths in PHP include/require statements. This can expose sensitive system files, configuration files, and other critical data.
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 Tooth Fairy plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Tooth Fairy' by AncoraThemes, or check the /wp-content/plugins/ directory for a tooth-fairy folderAffected if The plugin is installed and active
-
Identify the installed plugin versionIn WordPress admin, click on the Tooth Fairy plugin to view its details and version number, or read the main plugin PHP file header for the Version fieldAffected if The installed version is unknown, unpatched, or falls within any vulnerable version range
-
Verify the plugin exposes file inclusion functionalityCheck the plugin PHP files (typically in the main plugin file or includes directory) for any include/require statements that use user-supplied parameters without sanitization, looking for patterns like include($_GET['file']) or similar dynamic file inclusionAffected if The plugin code contains include/require statements that incorporate request parameters without proper path validation
-
Test for directory traversal exposureIf the plugin accepts file parameters via GET/POST requests, attempt a benign traversal test (e.g., parameter=value with ../../../../etc/passwd or similar path) on a non-production test instance, or review server access logs for traversal patterns directed at the plugin endpointsAffected if The plugin accepts and processes file path parameters that allow directory traversal sequences
-
Check for signs of exploitation in access logsReview web server access logs (Apache error.log, Nginx access.log) and WordPress audit logs for repeated requests containing ../ sequences targeting the Tooth Fairy plugin endpointsAffected if Logs show directory traversal attempts or suspicious file inclusion requests targeting the plugin
You are affected if the Tooth Fairy plugin by AncoraThemes is installed and its file inclusion functionality allows unauthenticated users to manipulate file paths via request parameters without proper validation.
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 Tooth Fairy when available. Until then, disable the plugin or implement web application firewall rules to block directory traversal patterns in request parameters.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22428 — 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-22428 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