CVE-2025-49277
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 unfoldwp Blogprise blogprise allows PHP Local File Inclusion.This issue affects Blogprise: from n/a through <= 1.0.9.
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 confidenceA PHP Local File Inclusion vulnerability exists in Blogprise theme <= 1.0.9 where user-supplied input is used in include/require statements without proper validation, allowing attackers to include arbitrary local PHP files and potentially achieve 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 Blogprise theme installationSearch for the 'blogprise' theme directory in your web application's wp-content/themes/ folder (if WordPress) or the equivalent themes directory for the CMS in use.Affected if The blogprise theme directory exists on the server.
-
Identify theme versionOpen the theme's style.css file (typically in the theme root) and locate the 'Version:' header field, or check for a version.php file within the theme directory that defines a version constant.Affected if The reported version number is 1.0.9 or lower.
-
Find file inclusion code patternsSearch the theme's PHP files for 'include', 'require', 'include_once', or 'require_once' statements that use variables directly (e.g., include $_GET['page']) rather than hardcoded values. Use grep or manually inspect common files like header.php, footer.php, page.php, and any template files that handle dynamic content.Affected if Any include/require statement uses unsanitized user input (from $_GET, $_POST, $_REQUEST, or similar superglobals) as the path to include.
-
Verify the vulnerable code is reachableDetermine if there are routes (URL parameters, admin settings, or template files) that trigger the vulnerable include/require code. Check if the affected PHP files are loaded during normal site operation or accessible via web requests.Affected if The vulnerable include/require code can be reached through a web request using crafted parameters.
You are affected if the Blogprise theme is installed with version 1.0.9 or lower AND the theme contains include/require statements using unsanitized user input that are reachable via web 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 to a patched version if available; otherwise disable the theme. Implement strict whitelist-based input validation for any file inclusion logic 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-49277 — 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-49277 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