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

CVE-2026-22439

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 AncoraThemes Green Planet green-planet allows PHP Local File Inclusion.This issue affects Green Planet: from n/a through <= 1.1.14.

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

This is a PHP Local File Inclusion (LFI) vulnerability in the AncoraThemes Green Planet WordPress theme (versions up to 1.1.14). The vulnerability stems from improper control of filenames used in PHP include/require statements, allowing attackers to include arbitrary local files via user-controlled input. This can lead to sensitive data exposure, code execution, or be chained with other vulnerabilities.

MitigationUpdate the Green Planet theme to the latest patched version. If no patch is available, disable the theme and implement input validation/sanitization on all file inclusion parameters. Additionally, configure PHP settings to disable allow_url_include and restrict open_basedir.

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 Green Planet theme is installed
    Check WordPress wp-content/themes directory for the green-planet theme folder, or list installed themes via WordPress admin interface or wp-cli command: wp theme list
    Affected if The Green Planet theme folder exists in the themes directory
  2. Determine installed theme version
    Locate the style.css file in the theme folder and read the Version: header in the file comments, or use wp-cli: wp theme get green-planet --fields=version
    Affected if The version number is 1.1.14 or lower (any version up to and including 1.1.14)
  3. Identify file inclusion code in theme
    Search PHP files within the theme folder for include, require, include_once, or require_once statements that use parameters from $_GET, $_POST, or $_REQUEST without proper sanitization
    Affected if File inclusion functions directly incorporate unsanitized user-supplied input without validation
  4. Check PHP mitigation settings
    Review PHP configuration (php.ini) for allow_url_include setting and open_basedir restriction, or run: php -i | grep -E 'allow_url_include|open_basedir'
    Affected if allow_url_include is enabled (set to On) and open_basedir is not configured to restrict file access

The environment is affected if the Green Planet theme version is 1.1.14 or lower AND the theme contains file inclusion logic using unsanitized user input from request parameters.

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

Update the Green Planet theme to the latest patched version. If no patch is available, disable the theme and implement input validation/sanitization on all file inclusion parameters. Additionally, configure PHP settings to disable allow_url_include and restrict open_basedir.

Recommended fix Moderate confidence

Latest version of Green Planet theme from AncoraThemes/Envato Market (newer than 1.1.14)

  1. Check AncoraThemes (Envato Market) for the latest version of the Green Planet theme
  2. Update the Green Planet theme to the latest available version from the official vendor (AncoraThemes/Envato Market)
  3. Verify the update was applied successfully by checking the theme version in WordPress admin under Appearance > Themes
  4. If no newer version is available from the vendor, consider alternative themes or contact AncoraThemes directly for a security patch
  5. As a hardening measure, ensure PHP execution is disabled in upload directories via .htaccess (AddHandler None)
Caveat Theme update may bring layout or feature changes; backup site before updating

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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