CVE-2025-47653
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 tggfref WP-Recall allows PHP Local File Inclusion. This issue affects WP-Recall: from n/a through 16.26.14.
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 Local File Inclusion (LFI) vulnerability in the tggfref component of the WP-Recall WordPress plugin allows attackers to include arbitrary PHP files from the server filesystem. This occurs due to improper control of filenames in include/require statements, enabling potential 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
- 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.
-
Locate WP-Recall plugin installation pathCheck the WordPress plugins directory (wp-content/plugins/) for the wp-recall folder, or query the WordPress database in the wp_options table for the option_name 'active_plugins' and look for 'wp-recall/index.php'Affected if The plugin folder wp-recall does not exist or is not active in WordPress
-
Identify installed WP-Recall versionOpen wp-content/plugins/wp-recall/index.php and locate the version definition (typically in a comment header or defined constant like 'RCL_VERSION'), or check the plugin metadata via WordPress admin Plugins pageAffected if The version number retrieved is lower than 16.26.15 (e.g., 16.26.10, 16.25.0, etc.)
-
Verify tggfref component existsCheck for the presence of the tggfref folder or file within the wp-recall plugin directory: ls wp-content/plugins/wp-recall/ | grep -i tggfref, or look for files referencing 'tggfref' using grep -r 'tggfref' wp-content/plugins/wp-recall/Affected if The tggfref component is present in the plugin directory, indicating the vulnerable code path exists
-
Inspect file inclusion behavior in tggfrefExamine PHP files within the tggfref component for include, require, include_once, or require_once statements that use unsanitized variables (e.g., include($_GET['file']) or include($path . $_REQUEST['filename']))Affected if Dynamic file inclusion statements are found that do not validate or restrict the included file path before passing user input
-
Check web server logs for exploitation attemptsReview Apache/Nginx access logs (typically in /var/log/apache2/access.log or /var/log/nginx/access.log) for requests to tggfref files with suspicious query parameters such as ?file=, ?path=, or ../ sequencesAffected if Recent access log entries show attempts to include files via tggfref with manipulated path parameters
You are affected if WP-Recall is installed with a version lower than 16.26.15 AND the tggfref component is present with vulnerable dynamic file inclusion code.
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 WP-Recall to version 16.26.15 or later. If no patch is available, implement strict input validation and allowlisting on file inclusion paths within the tggfref component, restricting includes to expected directories only.
- 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-47653 — 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-47653 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