CVE-2025-32663
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 roninwp FAT Cooming Soon fat-coming-soon allows PHP Local File Inclusion.This issue affects FAT Cooming Soon: from n/a through <= 1.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 · moderate confidenceLocal File Inclusion (LFI) vulnerability in the roninwp FAT Coming Soon WordPress plugin allows unauthenticated attackers to include arbitrary local PHP files through unsanitized input to include/require statements. This can be exploited to read sensitive files from the server filesystem or potentially achieve remote 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
- 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.
-
Identify if the roninwp FAT Coming Soon plugin is installedNavigate to WordPress admin dashboard > Plugins, or inspect the /wp-content/plugins/ directory for a folder containing 'roninwp' or 'fat-coming-soon' in the nameAffected if The plugin folder exists in the WordPress plugins directory
-
Determine the installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins and locate the version number listed for 'FAT Coming Soon' or 'roninwp FAT Coming Soon'. Alternatively, check the main plugin PHP file for a 'Version:' header commentAffected if The version cannot be determined or is earlier than the patched version
-
Check if the vulnerable file inclusion parameter is accessibleInspect the plugin's PHP files (particularly in the main plugin file and any files handling include/require operations) for functions that use user-supplied input in include, require, include_once, or require_once statements without proper sanitizationAffected if Unsanitized use of $_GET, $_POST, or similar superglobals in file inclusion functions is found in the plugin code
-
Verify the attack surface is reachableAttempt to access the plugin's frontend pages (the coming soon page) and check if URL parameters are passed to file inclusion functions. Look for parameters that might control which files are includedAffected if The plugin processes file path parameters from requests without validation
If the roninwp FAT Coming Soon plugin is installed and contains unsanitized file inclusion code accessible via web requests, the environment is affected by this LFI vulnerability.
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 dataApply any available vendor patch; if no patch exists, implement input validation/sanitization on all file inclusion functions to restrict included files to expected paths, or temporarily disable the plugin until a fix is available.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32663 — 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-32663 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