CVE-2025-49941
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 GlamChic glamchic allows PHP Local File Inclusion.This issue affects GlamChic: from n/a through <= 1.0.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 · high confidenceLocal File Inclusion vulnerability in AncoraThemes GlamChic theme allows attackers to include arbitrary local PHP files via unsanitized input to PHP include/require statements. This can lead to sensitive data exposure or remote code execution if attackers can upload files or access system resources.
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.
-
Identify if GlamChic theme is installedLocate the GlamChic theme directory in your CMS installation, typically under wp-content/themes/glamchic or the themes directory. Check for theme configuration files like style.css containing 'GlamChic' or 'AncoraThemes'.Affected if The GlamChic theme by AncoraThemes is present in your environment
-
Find PHP files with include/require statementsSearch the GlamChic theme directory for PHP files containing 'include(', 'require(', 'include_once(', or 'require_once(' statements. Use grep or similar: grep -r "include\|require" path/to/glamchic/theme/Affected if PHP files with file inclusion functions exist in the theme
-
Check for user input reaching include/requireExamine identified inclusion files for direct use of $_GET, $_POST, $_REQUEST, or URL parameters in include/require statements without sanitization. Look for patterns like: include($_GET['file']), require($var), or include($_REQUEST['template']).Affected if User-supplied parameters are used directly in include or require statements without validation
-
Verify absence of input validationIn files using user input in inclusions, check if there is any whitelist validation, basename(), or path traversal prevention (such as checking for '..' or '/') before the inclusion. Inspect code for functions like in_array(), preg_match for allowed values, or realpath() validation.Affected if No input validation, whitelisting, or path sanitization is performed before file inclusion
-
Confirm accessible upload or system accessIf the LFI is present, determine if attackers can influence the included file path. Check if file upload functionality exists in the theme or if system files are readable via the vulnerable parameter.Affected if Attackers can control the file path through URL parameters or upload functionality exists
Your environment is affected if the AncoraThemes GlamChic theme is installed AND contains PHP files where user input (via GET/POST parameters) reaches include/require statements without validation or sanitization.
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 dataImplement strict input validation using whitelist approach for file inclusions, disable allow_url_include, and ensure all user-supplied parameters are validated against an allowlist of permitted values before use in include/require statements.
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49941 — 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-49941 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