CVE-2025-23952
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 ntm custom-field-list-widget custom-field-list-widget allows PHP Local File Inclusion.This issue affects custom-field-list-widget: from n/a through <= 1.5.1.
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 (LFI) vulnerability in the ntm custom-field-list-widget WordPress plugin (versions <= 1.5.1) allows attackers to include arbitrary local files due to improper control of filename parameters in include/require statements. This can lead to disclosure of sensitive files or potentially remote code execution if attackers can upload malicious PHP files.
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.
-
Confirm plugin installationCheck if the ntm custom-field-list-widget plugin directory exists in the WordPress plugins folder (wp-content/plugins/). Look for a folder named 'ntm-custom-field-list-widget' or similar containing the plugin files.Affected if The plugin directory exists in the WordPress installation.
-
Identify installed versionOpen the main plugin PHP file (usually named similarly to the plugin folder) and locate the plugin header comment which contains the Version field. Alternatively, check the readme.txt file for the version number.Affected if The installed version is 1.5.1 or lower.
-
Verify plugin is activeLog into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Check whether the ntm custom-field-list-widget plugin is activated.Affected if The plugin is active on the WordPress site.
-
Check for vulnerable file inclusion codeExamine the plugin PHP files for include(), require(), include_once(), or require_once() statements that use variables for file paths without proper sanitization. Look for patterns like 'include($var)' or 'require($_GET[...])'.Affected if The plugin contains file inclusion functions using unsanitized variable input.
The environment is affected if the ntm custom-field-list-widget plugin versions 1.5.1 or lower is installed and active on the WordPress site.
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 the ntm custom-field-list-widget plugin to the latest patched version. If no update is available, disable the plugin until a fix is released. Alternatively, implement strict input validation and whitelist-based file inclusion logic to prevent path traversal.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23952 — 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-23952 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