CVE-2025-49364
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 Ludos Paradise ludos-paradise allows PHP Local File Inclusion.This issue affects Ludos Paradise: from n/a through <= 2.1.3.
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 Ludos Paradise theme allows attackers to include arbitrary PHP files from the local server due to improper control of filename parameters in include/require statements. This can lead to sensitive file disclosure or remote code execution.
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 Ludos Paradise theme filesSearch the web server document root for the 'ludos-paradise' or 'Ludos-Paradise' theme directory, typically under wp-content/themes/ for WordPress or the themes folder of the respective CMSAffected if The theme directory exists on the server
-
Identify the theme versionOpen the theme's style.css, functions.php, or theme.json file and locate the version declaration in the header comments or metadataAffected if The installed version falls within the vulnerable version range and has not been patched
-
Find include/require statements using dynamic variablesSearch the theme's PHP files (especially in functions.php, header.php, and any template files) for include, include_once, require, or require_once statements that use variables directly in the path argument without sanitization (e.g., include($file); include($_GET['page']);)Affected if Dynamic file includes exist that could accept user-supplied input without validation
-
Verify user input reaches the file inclusionExamine the identified include/require code paths to determine if request parameters (GET, POST, COOKIE) or server variables are passed to the file inclusion function without filteringAffected if Unsanitized user input from HTTP requests can reach the include/require function
-
Check if the theme is actively runningVerify the theme is currently loaded/active on the website by checking the CMS configuration or theme settingsAffected if The vulnerable theme version is actively loaded and accessible to attackers
The environment is affected if Ludos Paradise theme is installed with a vulnerable version and contains unsanitized include/require statements that accept user-controlled input from 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 dataUpgrade Ludos Paradise to the latest version that addresses this vulnerability. If no patch is available, audit all include/require statements to implement proper input validation and path traversal protections.
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49364 — 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-49364 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