CVE-2025-49943
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 Femme femme allows PHP Local File Inclusion.This issue affects Femme: from n/a through <= 1.3.11.
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 confidenceLocal File Inclusion vulnerability in the Femme theme by AncoraThemes allows attackers to include arbitrary local files from the server filesystem via improper control of filename parameters in PHP include/require statements. This can enable exposure of sensitive configuration files, credentials, source code, and 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.
-
Confirm Femme theme installationCheck your WordPress themes directory (wp-content/themes/femme) or look for 'AncoraThemes' and 'Femme' in your theme header files (style.css or theme.json)Affected if The Femme theme by AncoraThemes is installed on the WordPress site
-
Identify Femme theme versionOpen the theme's style.css file in the femme theme folder and locate the 'Version:' declaration in the theme header commentAffected if The installed version is older than the patched version (check against the latest available version from AncoraThemes)
-
Locate vulnerable file inclusion codeSearch PHP files in the femme theme folder for include, require, include_once, or require_once statements that use variables from $_GET, $_POST, or $_REQUEST without sanitization (e.g., grep for 'include.*\$_GET', 'require.*\$_REQUEST')Affected if Any PHP file contains include/require using unsanitized user input from query parameters
-
Check for exposed template/parameter handlersExamine index.php, header.php, or custom PHP files that handle page template loading via URL parameters (common parameter names: template, page, file, path, theme, style)Affected if The theme accepts a parameter to load external files and passes it directly to include/require without validation
If the Femme theme is installed and contains PHP code that uses user-supplied input in include/require statements without validation, the environment is vulnerable to LFI attacks.
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 Femme theme to the latest patched version. If no patch available, implement strict input validation using whitelist approaches for any file inclusion logic, disable allow_url_include, and ensure all user-supplied parameters are sanitized before use in include/require statements.
- Consultation4.0 h
- Implementation10.0 h
- Testing6.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 $6,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49943 — 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-49943 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