CVE-2025-49436
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 CocoBasic Anotte anotte-wp allows PHP Local File Inclusion.This issue affects Anotte: from n/a through <= 1.8.
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 in the CocoBasic Anotte WordPress theme (versions 1.8 and below) allows attackers to include arbitrary local files from the server due to improper validation of user-supplied input used in include/require statements. This can enable unauthorized reading of sensitive files such as 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.
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.
-
Locate Anotte theme installationCheck the wp-content/themes/ directory for the anotte folderAffected if The anotte theme directory exists in your WordPress installation
-
Determine installed versionOpen the theme's style.css file (located in wp-content/themes/anotte/) and look for the 'Version:' comment in the file headerAffected if The version listed is 1.8 or below
-
Find vulnerable include/require codeSearch all PHP files in the theme directory for include(), require(), include_once(), or require_once() statements that reference $_GET, $_POST, or $_REQUEST parameters without sanitizationAffected if User-controlled parameters are used directly in include/require statements without validation
-
Identify the vulnerable parameterExamine the vulnerable include/require code found in the previous step to identify which URL parameter controls the file inclusion (commonly named 'file', 'page', 'template', or similar)Affected if A parameter accepting user input controls the file path in an include/require statement
-
Test for LFI exploitabilitySend a crafted HTTP request with a path traversal payload (e.g., ?file=../../../../etc/passwd) to a page using the theme and observe if file contents are returnedAffected if The server returns contents of files outside the theme directory
-
Check file permissionsVerify that sensitive files (wp-config.php, .env, /etc/passwd) are readable by the web server processAffected if The web server user can read sensitive system or configuration files that should be restricted
You are affected if the Anotte theme version is 1.8 or below AND your installation contains the vulnerable unvalidated include/require code that allows path traversal via URL parameters.
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 Anotte theme; if unavailable, implement strict input validation on all include/require parameters, disable allow_url_include in PHP configuration, and ensure web root files have minimal permissions.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49436 — 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-49436 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