CVE-2026-25326
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 cmsmasters CMSMasters Content Composer cmsmasters-content-composer allows PHP Local File Inclusion.This issue affects CMSMasters Content Composer: from n/a through <= 1.4.5.
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 confidenceA PHP Local File Inclusion vulnerability in the CMSMasters Content Composer plugin allows attackers to include and execute local files through unsanitized input parameters, potentially exposing sensitive system files or achieving 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/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.
-
Verify CMSMasters Content Composer is installedCheck your WordPress plugins directory or wp-content/plugins/ for the cmsmasters-content-composer folder, or query the WordPress database: SELECT plugin_name FROM wp_plugins WHERE plugin_name LIKE '%cmsmasters%';Affected if The plugin folder cmsmasters-content-composer exists in the plugins directory or the plugin appears in WordPress database query results
-
Identify installed plugin versionOpen wp-content/plugins/cmsmasters-content-composer/readme.txt and locate the 'Version:' field, or check the plugin header in its main PHP file for the 'Version' commentAffected if The version number found is lower than the patched version (no patched version specified in CVE data)
-
Check PHP allow_url_include settingCreate a PHP info file (<?php phpinfo(); ?>) or check your php.ini for the directive: allow_url_include = OnAffected if allow_url_include is enabled (set to On), which increases exploit severity
-
Inspect web server access logs for LFI indicatorsSearch access logs (usually in /var/log/apache2/ or /var/log/nginx/) for patterns like '?load_template=' or '?file=' or '../' pointing to the Content Composer plugin endpointAffected if Suspicious requests with directory traversal sequences (..) or file path parameters targeting the plugin are present in logs
-
Verify plugin admin access controlsAttempt to access known Content Composer endpoints or check wp-content/plugins/cmsmasters-content-composer/ for files handling file inclusion (search for 'include', 'require', 'load_template' functions)Affected if The plugin exposes file inclusion functions without proper admin authentication checks
You are affected if CMSMasters Content Composer plugin is installed AND the installed version is unpatched AND the vulnerable file inclusion functionality is accessible to attackers.
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 to a patched version of CMSMasters Content Composer when released; in the interim, disable the plugin if possible, ensure PHP allow_url_include is off, and implement web server-level restrictions.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25326 — 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-2026-25326 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