CVE-2025-49361
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 Mamita mamita allows PHP Local File Inclusion.This issue affects Mamita: from n/a through <= 1.0.9.
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 AncoraThemes Mamita WordPress theme (versions <= 1.0.9). The vulnerability stems from improper control of filenames in include/require statements, allowing attackers to manipulate file path parameters to include arbitrary local files from the server, potentially leading to code execution or sensitive data disclosure.
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 Mamita theme is installedLocate the Mamita theme directory in your WordPress installation at wp-content/themes/mamita/ by listing the themes folder or checking via WordPress admin Appearance > ThemesAffected if The mamita directory exists in wp-content/themes/
-
Identify installed theme versionOpen wp-content/themes/mamita/style.css and locate the 'Version:' field in the theme header comment blockAffected if The version listed is 1.0.9 or lower
-
Search for file inclusion code patternsInspect PHP files within wp-content/themes/mamita/ for dynamic include(), require(), include_once(), or require_once() statements that use variables or parameters in the file pathAffected if Any include/require statements accept user-controlled input as all or part of the file path
-
Identify the vulnerable parameterReview the identified inclusion statements to determine which GET, POST, or request parameters are used to construct the file path and whether they can be manipulatedAffected if A parameter controlling the file path can be manipulated to traverse directories (e.g., ../../) or include arbitrary local files
-
Verify the vulnerability is exploitableTest the identified parameter with a benign path such as ../../wp-config.php or /etc/passwd (if the server OS permits) to confirm arbitrary file inclusion is possibleAffected if The parameter successfully reads files outside the intended directory or theme scope
A defender is affected if the Mamita WordPress theme version 1.0.9 or lower is installed AND the theme contains include/require statements that accept user-supplied file path parameters without proper validation.
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 Mamita theme when available. If no patch exists, implement strict input validation and path sanitization on any file inclusion parameters, and consider disabling allow_url_include in PHP configuration as a defense-in-depth measure.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49361 — 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-49361 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