CVE-2025-49383
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 CocoBasic Neresa neresa-wp allows PHP Local File Inclusion.This issue affects Neresa: from n/a through <= 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 · moderate confidenceThis is a PHP Local File Inclusion (LFI) vulnerability in the CocoBasic Neresa WordPress theme (version 1.3 and below). The vulnerability allows authenticated or unauthenticated attackers to include arbitrary PHP files from the server file system, potentially leading to sensitive file disclosure (like wp-config.php) or remote code execution if an attacker can control the included 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 if Neresa theme is installedCheck for the presence of the Neresa theme directory in your WordPress installation at /wp-content/themes/neresa/Affected if The neresa theme directory exists in the themes folder
-
Determine the installed Neresa theme versionOpen the style.css file in /wp-content/themes/neresa/ and locate the 'Version:' header in the theme comments, or check theme.json if present for a version fieldAffected if The reported version is 1.3 or lower
-
Check for vulnerable include/require code patternsSearch the Neresa theme PHP files for include, require, include_once, or require_once statements that use user-supplied input (such as $_GET, $_POST, or $_REQUEST variables) without proper sanitizationAffected if The theme contains include/require statements that directly incorporate unsanitized request parameters
-
Verify PHP allow_url_include settingCheck your php.ini file or run 'php -i' and look for the allow_url_include directiveAffected if allow_url_include is set to On (1), which would allow URL-based file inclusion in addition to local file inclusion
-
Test for unauthenticated access to vulnerable endpointsReview the theme's PHP files for any AJAX handlers or direct-access scripts that process include/require parameters without requiring authenticationAffected if The theme exposes include/require functionality to unauthenticated users
You are affected if the Neresa theme version is 1.3 or lower AND the theme contains include/require code that processes unsanitized user input, especially if accessible to unauthenticated users.
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 the Neresa theme to the latest patched version. If no update is available, disable or remove the theme. Additionally, ensure PHP configuration sets allow_url_include=0 and allow_url_fopen=0, and audit the theme code for proper input validation on include/require statements.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49383 — 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-49383 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