CVE-2025-49363
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 Kings & Queens kings-queens allows PHP Local File Inclusion.This issue affects Kings & Queens: from n/a through <= 1.1.16.
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 confidenceThe Kings & Queens WordPress theme by AncoraThemes contains a PHP Local File Inclusion (LFI) vulnerability. Attackers can manipulate filename parameters in include/require statements to read arbitrary files from the server's filesystem, potentially exposing sensitive configuration files, credentials, or source code.
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 Kings & Queens theme installationCheck the WordPress themes directory (wp-content/themes/) for the presence of the 'kings-queens' or 'kings-and-queens' theme folder. List the contents to verify the theme is installed.Affected if The kings-queens theme folder exists in wp-content/themes/
-
Identify installed theme versionOpen the style.css file within the Kings & Queens theme folder and locate the 'Version:' header in the file header comments. Note the version number for comparison.Affected if The theme version cannot be determined or is lower than the patched version provided by AncoraThemes.
-
Search for insecure file inclusion patternsSearch all PHP files within the Kings & Queens theme folder for patterns where include, include_once, require, or require_once functions use variables derived from $_GET, $_POST, or $_REQUEST without sanitization. Use grep or a code search tool to find patterns like 'include($', 'require($', 'include($_', 'require($_' followed by user-supplied input.Affected if PHP files in the theme contain include/require statements that directly use unsanitized user input parameters.
-
Identify exposed file inclusion parametersReview identified vulnerable include/require code to determine which URL parameters control the file path. Test if these parameters accept directory traversal sequences like '../' to access files outside the theme directory.Affected if URL parameters controlling file inclusion accept directory traversal sequences and can be manipulated via HTTP requests.
A user is affected if the Kings & Queens theme is installed, contains PHP files with insecure include/require usage using unsanitized user input, and the vulnerable parameter is accessible via HTTP requests.
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 theme if available; otherwise, implement strict input validation and whitelist-based filtering on all file inclusion parameters, and ensure allow_url_include is disabled in PHP configuration.
- 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-49363 — 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-49363 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