CVE-2025-39411
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 Indie_Plugins WhatsApp Click to Chat Plugin for WordPress wpt-whatsapp.This issue affects WhatsApp Click to Chat Plugin for WordPress: from n/a through <= 2.2.12.
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 Remote File Inclusion (RFI) vulnerability in the Indie_Plugins WhatsApp Click to Chat WordPress plugin (versions <= 2.2.12) allows attackers to include remote files via improperly validated input in PHP include/require statements, potentially leading to arbitrary 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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 plugin presenceNavigate to WordPress admin dashboard > Plugins > Installed Plugins, or check the /wp-content/plugins/ directory for a folder named 'whatsapp-click-to-chat' or similar Indie_Plugins WhatsApp plugin folderAffected if The Indie_Plugins WhatsApp Click to Chat plugin is found in the WordPress installation
-
Check installed versionIn WordPress admin, view the plugin details to see the version number, or open the main plugin PHP file (usually plugin-name.php) and look for the 'Version' header in the plugin commentsAffected if The installed version is 2.2.12 or any earlier version
-
Identify vulnerable code patternsExamine PHP files in the plugin directory for include(), require(), include_once(), or require_once() statements that use unsanitized variables from $_GET, $_POST, or $_REQUEST as file pathsAffected if The plugin contains include/require statements that incorporate user-supplied input without validation
-
Test for RFI exposureIf the vulnerable parameter is identifiable, send a benign request with a controlled URL (e.g., ?file=http://example.com) and observe if the server attempts to fetch or include the external fileAffected if The plugin allows inclusion of remote URLs through user-controllable parameters
-
Review access logsSearch web server access logs (Apache/nginx) for requests to the plugin that contain http:// or https:// in query parameters related to file pathsAffected if Logs show requests attempting to include remote files through the plugin's parameters
A user is affected if the WordPress site has the Indie_Plugins WhatsApp Click to Chat plugin installed at version 2.2.12 or lower AND the plugin contains include/require statements that use unsanitized user input as file paths.
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 plugin to the latest version if available, or implement strict input validation on file path parameters used in include/require statements to prevent arbitrary file inclusion.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-39411 — 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-39411 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