CVE-2025-49370
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 Lymcoin lymcoin allows PHP Local File Inclusion.This issue affects Lymcoin: from n/a through <= 1.3.12.
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 confidenceA PHP Local File Inclusion vulnerability in the AncoraThemes Lymcoin theme (versions <= 1.3.12) allows remote attackers to include arbitrary local files via improperly validated input in include/require statements. This can lead to sensitive file disclosure and potentially remote code execution if attackers can upload or access malicious PHP 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.
-
Identify installed Lymcoin theme versionLocate the theme's style.css file in wp-content/themes/lymcoin/ and check the 'Version:' header in the file comments. Alternatively, check version in functions.phpAffected if version number is 1.3.12 or lower (or if version cannot be determined but theme is confirmed as Lymcoin)
-
Search for dynamic include/require usageGrep the theme's PHP files (especially functions.php, template files, and any files in subdirectories) for patterns like 'include(', 'require(', 'include_once(', 'require_once(' that use variables such as $_GET, $_POST, $_REQUEST, or other user-supplied inputAffected if any include/require statements directly use unsanitized user input parameters
-
Inspect the affected include/require statementsFor each dynamic include/require found, examine the code path to determine if the user input is passed directly to the include/require without validation, or if it undergoes any validation before being usedAffected if the include/require parameter takes raw user input without allowlist filtering, path sanitization, or basename() checks
-
Verify if the application is publicly accessibleConfirm the WordPress site using this theme is accessible over the network (not localhost-only)Affected if the site is publicly accessible, making the LFI exploitable by remote attackers
You are affected if the Lymcoin theme version is 1.3.12 or lower AND your site has PHP files containing include/require statements that directly incorporate unsanitized user input from request parameters.
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 dataApply a vendor patch if available; otherwise, implement strict input validation using allowlist-based filtering on all include/require statement parameters to prevent path traversal and unauthorized file inclusion.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49370 — 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-49370 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