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

CVE-2025-14502

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/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
The News and Blog Designer Bundle plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.1 via the template parameter. This makes it possible for unauthenticated attackers to include and execute arbitrary .php files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where .php file types can be uploaded and included.

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 News and Blog Designer Bundle WordPress plugin is vulnerable to unauthenticated local file inclusion via the template parameter in all versions up to 1.1, allowing attackers to include and execute arbitrary .php files on the server for remote code execution.

MitigationUpdate to the latest patched version of the plugin; if unavailable, disable the plugin. Additionally, restrict file inclusion permissions and disable allow_url_include on the server as a defense-in-depth measure.

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/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 the plugin is installed
    Check for the presence of the News and Blog Designer Bundle plugin in the WordPress installation at /wp-content/plugins/news-and-blog-designer-bundle/ or via WP admin plugin list
    Affected if The plugin directory exists in the WordPress plugins folder
  2. Determine installed plugin version
    Open the main plugin file (typically news-and-blog-designer-bundle.php) and locate the Version header in the plugin comment block, or check the plugin metadata via WordPress admin under Plugins > Installed Plugins
    Affected if The installed version is 1.1 or any version lower (the vulnerability affects all versions up to 1.1)
  3. Locate the vulnerable template handler
    Search the plugin directory for files that handle a 'template' parameter, commonly in files related to template loading, rendering, or file inclusion logic
    Affected if A PHP file exists that processes the template parameter without proper sanitization
  4. Confirm the LFI is unauthenticated
    Attempt to access the identified template-handling endpoint without logging in, using a request like ?template=../../../../wp-config.php or similar path traversal to test if arbitrary files can be included
    Affected if The endpoint responds and includes files without requiring authentication
  5. Check server configuration for file inclusion risk
    Inspect php.ini for allow_url_include=1 and verify file permissions on the web root allow the plugin to read sensitive files
    Affected if allow_url_include is enabled or the web server user can read sensitive files outside the web root

A user is affected if the News and Blog Designer Bundle plugin version 1.1 or lower is installed and the vulnerable template parameter handler is accessible without authentication, allowing path traversal to include arbitrary .php files.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest patched version of the plugin; if unavailable, disable the plugin. Additionally, restrict file inclusion permissions and disable allow_url_include on the server as a defense-in-depth measure.

Recommended fix Moderate confidence

Latest version of News and Blog Designer Bundle on wordpress.org (version > 1.1)

  1. Check the current version of the News and Blog Designer Bundle plugin installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate News and Blog Designer Bundle and note the current version number
  4. Visit the WordPress plugin repository at wordpress.org/plugins/news-and-blog-designer-bundle/ to identify the latest available version
  5. If the latest version is higher than 1.1, update the plugin to the latest version via Plugins > Installed Plugins > Update Now
  6. If no update is available from the WordPress repository, contact the plugin vendor directly for a patched version
  7. Verify the update was successful and test that the template functionality still works correctly
  8. Ensure WordPress core and all other plugins are kept up to date

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14502 — 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-14502 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