GreenyWordPress extension · Axiomthemes
CVE-2025-53441
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 Greeny greeny allows PHP Local File Inclusion.This issue affects Greeny: from n/a through <= 2.6.
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 confidenceThis is a PHP Local File Inclusion (LFI) vulnerability in the Greeny WordPress theme. The vulnerability allows attackers to manipulate file path parameters in include/require statements to read sensitive local files from the server, potentially exposing configuration files, credentials, or system files.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
GreenyWordPress extension
<= 2.6CVSS 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.
-
Check if Greeny theme is installedNavigate to wp-content/themes/ in your WordPress installation directory. Look for a folder named 'greeny' or 'Greeny'. If present, the theme is installed.Affected if The Greeny theme folder exists in the themes directory.
-
Determine the installed version of Greeny themeOpen the style.css file located in the Greeny theme folder. Look for a 'Version:' header in the file comments near the top. Alternatively, check theme.json or version.php if they exist in the theme folder.Affected if The version listed is 2.6 or lower.
-
Identify vulnerable file inclusion codeSearch the Greeny theme folder for PHP files containing include, include_once, require, or require_once statements that use variables in the file path (for example: include($some_variable); or require($_GET['param']);). Examine the theme's PHP files for dynamic file inclusion patterns.Affected if PHP files contain include/require statements that incorporate user-controlled or unsanitized variables into file paths.
-
Locate the specific vulnerable parameterReview the identified file inclusion code for parameters that accept file paths without strict validation. Common parameter names in LFI vulnerabilities include 'file', 'path', 'page', 'template', 'include', or similar. Check if these parameters are used directly in include/require statements.Affected if A parameter accepting file paths is used directly in include/require statements without validation or sanitization.
You are affected if the Greeny theme version is 2.6 or lower AND the theme contains PHP files with include/require statements that use unsanitized variables from user input in file paths.
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 the Greeny theme to the latest patched version. If no update is available, implement strict input validation and whitelist-based filtering on all file inclusion parameters in the theme's PHP code.
Fix this in Greeny
Scoped from the published advisory
- 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-2025-53441 — 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-2025-53441 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