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

CVE-2025-4414

HIGH · 8.1 CVSS v3.1 Published 2025-07-04
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 cmsmasters CMSMasters Content Composer cmsmasters-content-composer allows PHP Local File Inclusion.This issue affects CMSMasters Content Composer: from n/a through < 2.5.7.

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

This is a PHP Local File Inclusion (LFI) vulnerability in CMSMasters Content Composer plugin. The vulnerability allows attackers to manipulate file inclusion paths via unsanitized user input in include/require statements, potentially leading to remote code execution or unauthorized access to sensitive server files.

MitigationUpdate CMSMasters Content Composer to version 2.5.7 or later. If immediate patching is not possible, disable the plugin or implement WAF rules to block malicious include path parameters.

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. Locate CMSMasters Content Composer plugin installation
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'cmsmasters-content-composer' or similar CMSMasters plugin directories. If using a theme bundle, check the theme includes/plugins folder.
    Affected if The plugin directory exists on the server.
  2. Identify the installed plugin version
    Open the main plugin PHP file (usually named like cmsmasters-content-composer.php or plugin.php) and look for a version comment or constant at the top. Alternatively, check the readme.txt file in the plugin folder for the 'Stable tag' or 'Version' entry.
    Affected if The version number found is below 2.5.7 (e.g., 2.5.6, 2.5.5, older).
  3. Verify vulnerable include/require code patterns exist
    Search the plugin PHP files for include, require, include_once, or require_once statements that use variable parameters without proper sanitization. Look for patterns like 'include($param)', 'require($_GET[...])', or similar unsanitized user input in file inclusion functions.
    Affected if Files contain include/require statements using raw user input (GET/POST parameters) without sanitization functions like realpath(), basename(), or whitelist validation.
  4. Confirm the plugin functionality is active
    Check if the plugin is activated in WordPress admin under Plugins > Installed Plugins, or verify the plugin code is being loaded (check wp-options table for active_plugins or the theme's functions.php for plugin activation).
    Affected if The plugin is activated and its code is executing on the site.

If CMSMasters Content Composer is installed, activated, and the version is below 2.5.7 with unsanitized include/require patterns present in the code, the environment is vulnerable to CVE-2025-4414.

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 CMSMasters Content Composer to version 2.5.7 or later. If immediate patching is not possible, disable the plugin or implement WAF rules to block malicious include path parameters.

Recommended fix Moderate confidence

2.5.7

  1. Check the current installed version of CMSMasters Content Composer in your WordPress installation (typically in wp-content/plugins/cmsmasters-content-composer/ or through the WordPress admin plugin list)
  2. Backup your entire WordPress site including database and files before performing any upgrade
  3. Download CMSMasters Content Composer version 2.5.7 or later from the official WordPress plugin repository or from a trusted source
  4. Either use the WordPress admin dashboard to update the plugin (Plugins > Add New > Upload, or Updates section), or replace the cmsmasters-content-composer directory via FTP/SFTP with the new version
  5. Verify the update was successful by checking the installed version number
  6. Test critical functionality on your site to ensure the plugin continues to work correctly after the update

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
14.0 hours of engineering $2,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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