dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2025-31082

HIGH · 8.1 CVSS v3.1 Published 2025-04-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in InfornWeb News & Blog Designer Pack blog-designer-pack allows PHP Local File Inclusion.This issue affects News & Blog Designer Pack: from n/a through <= 4.0.

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 confidence

The InfornWeb News & Blog Designer Pack plugin (blog-designer-pack) through version 4.0 contains a PHP Local File Inclusion (LFI) vulnerability due to improper control of filename parameters in include/require statements. Attackers can manipulate file path parameters to include arbitrary PHP files, potentially leading to remote code execution or sensitive file disclosure.

MitigationUpdate to a patched version of the plugin as soon as available. If no patch exists, disable the plugin immediately and implement a Web Application Firewall (WAF) as a temporary compensating control. Review server file permissions and ensure PHP configuration disables allow_url_include.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify plugin installation status
    Check if the blog-designer-pack plugin is installed and active in WordPress. This can be done via the WordPress admin dashboard under Plugins > Installed Plugins, or by checking the /wp-content/plugins/ directory for the blog-designer-pack folder.
    Affected if The plugin is installed and active on the WordPress site.
  2. Determine installed plugin version
    Locate the main plugin file (typically blog-designer-pack.php or similar in the plugin directory) and check the Version header in the file comments. Alternatively, check the readme.txt file for the version declaration.
    Affected if The installed version is 4.0 or any version lower than 4.0, since the vulnerability affects through version 4.0.
  3. Identify vulnerable include/require patterns
    Search the plugin PHP files for include, require, include_once, or require_once statements that use variables or parameters in the file path without proper sanitization. Focus on files in the include/ directory mentioned in the CVE summary.
    Affected if The plugin code contains include/require statements that incorporate user-controllable input into file paths without validation.
  4. Inspect for LFI-prone parameter usage
    Review PHP files that handle file path parameters (often named like 'file', 'path', 'template', 'page', 'layout', or similar) and trace whether these parameters flow into include/require statements without sanitization.
    Affected if File path parameters are used directly in include/require statements without validation or sanitization routines.
  5. Check plugin configuration and exposure
    Examine if the vulnerable code paths are accessible without authentication or only require subscriber-level access. Review the plugin's publicly accessible PHP files and AJAX handlers.
    Affected if The vulnerable file inclusion code is reachable without proper authentication or with low-privilege user access.

A user is affected if the blog-designer-pack plugin is installed at version 4.0 or lower and the plugin code contains include/require statements that use unsanitized file path parameters controllable by attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version of the plugin as soon as available. If no patch exists, disable the plugin immediately and implement a Web Application Firewall (WAF) as a temporary compensating control. Review server file permissions and ensure PHP configuration disables allow_url_include.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-31082 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-31082 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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