CVE-2025-53433
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 EasyEat easyeat allows PHP Local File Inclusion.This issue affects EasyEat: from n/a through <= 1.9.0.
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 · high confidenceLocal File Inclusion (LFI) vulnerability in AncoraThemes EasyEat theme allows attackers to manipulate file inclusion paths in PHP include/require statements, potentially executing arbitrary PHP code by including malicious local files.
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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/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.
-
Identify if EasyEat theme is installedLocate the theme directory in the web root (commonly wp-content/themes/easyeat or similar). Check for theme folder existence.Affected if The EasyEat theme by AncoraThemes is present in the WordPress themes directory.
-
Determine EasyEat theme versionOpen the style.css file in the theme directory and read the 'Version:' header, or check theme.php for version definition.Affected if The installed version matches or precedes the affected unpatched version range.
-
Locate vulnerable include/require statementsSearch PHP files in the theme directory for dynamic include/require statements using variables or user input (e.g., include($_GET['file'], require($_REQUEST['template']).'.php').Affected if Dynamic file inclusion using unsanitized request parameters exists in theme PHP files.
-
Verify parameter accessibilityTest if the vulnerable parameter (commonly 'file', 'page', 'template', or similar) can be controlled via GET or POST requests to the affected page.Affected if User-supplied input directly reaches include/require without validation.
-
Check PHP configuration settingsReview php.ini for allow_url_include setting (should be Off for LFI mitigation).Affected if allow_url_include is enabled, which can exacerbate LFI impact.
You are affected if the EasyEat theme is installed, the version is within the vulnerable range, and dynamic file inclusion using unsanitized user input exists in the theme code.
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 EasyEat theme to patched version; if unavailable, implement strict input validation on include/require parameters and disable allow_url_include in PHP configuration.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-53433 — 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-53433 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