CVE-2025-69077
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 Hobo hobo allows PHP Local File Inclusion.This issue affects Hobo: from n/a through <= 1.0.10.
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 PHP Local File Inclusion (LFI) vulnerability exists in the AncoraThemes Hobo theme (version <= 1.0.10) due to improper control of filenames in include/require statements. This allows attackers to potentially include and execute malicious PHP files from the local server by manipulating file path parameters.
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 Hobo theme installationLocate the theme directory - typical paths include /wp-content/themes/hobo/ or /themes/hobo/. Check for the existence of theme files such as style.css, functions.php, or index.php within this directory.Affected if The Hobo theme files are present on the server.
-
Identify Hobo theme versionOpen the theme's style.css file (usually at /wp-content/themes/hobo/style.css) and locate the 'Version:' header in the file comment block. Compare this version number to 1.0.10.Affected if The installed version is 1.0.10 or lower.
-
Search for vulnerable include/require patternsExamine PHP files in the theme directory (particularly functions.php, header.php, footer.php, and any files in includes/ or templates/ subdirectories) for include(), require(), include_once(), or require_once() statements that use variables in the file path without sanitization.Affected if Code contains include/require statements that incorporate user-controlled input directly into file paths without validation.
-
Identify exposed file inclusion parametersReview the theme's PHP files for parameters (typically via $_GET, $_POST, or $_REQUEST) used in include/require calls. Check if these parameters accept full paths, relative paths, or path traversal sequences (such as ../).Affected if URL parameters or form inputs can influence file paths used in include/require statements without proper filtering.
You are affected if the Hobo theme version is 1.0.10 or lower AND your server exposes PHP file inclusion functionality that allows manipulation of file paths through user input.
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 Hobo theme. If no update is available, implement strict input validation on file inclusion parameters, use whitelist-based file inclusion, and ensure directory traversal protections are in place.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-69077 — 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-69077 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