CVE-2025-47693
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 Services Booking fat-services-booking allows PHP Local File Inclusion.This issue affects FAT Services Booking: from n/a through <= 5.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 · high confidenceA PHP Local File Inclusion (LFI) vulnerability in the roninwp FAT Services Booking plugin (versions <= 5.5) allows attackers to include arbitrary local files via improper control of filename parameters in include/require statements. This occurs due to insufficient validation of user-supplied input before passing it to PHP's include/require functions.
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.
-
Confirm the FAT Services Booking plugin is installedAccess your WordPress admin panel, navigate to Plugins > Installed Plugins, and look for 'FAT Services Booking' by roninwp in the listAffected if The plugin is not found in the installed plugins list, then you are not affected by this specific CVE
-
Identify the installed plugin versionIn the WordPress admin, click on the plugin from the Installed Plugins list to view its details, or check the plugin's main PHP file header for the 'Version' tagAffected if The version number is 5.5 or lower (for example, 5.5, 5.4, 5.3, etc.)
-
Verify web server access logs for suspicious include/require requestsReview your web server access logs (Apache, Nginx, or PHP-FPM) for requests containing '../' directory traversal sequences or direct file paths in query parameters targeting the plugin's PHP filesAffected if Log entries show repeated requests with directory traversal patterns (like ../../) or absolute file paths (like /etc/passwd) directed at the plugin's inclusion functions
-
Test for LFI vulnerability via exposed parametersIf you have authorization, send a crafted GET or POST request to the plugin's endpoints using a parameter that performs file inclusion, attempting to include a known file such as /etc/passwd or wp-config.phpAffected if The response returns contents of files outside the web root, confirming arbitrary file inclusion is possible
You are affected if the FAT Services Booking plugin is installed with version 5.5 or lower and remote attackers can access the vulnerable file inclusion mechanism without authentication.
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 dataUpgrade to a patched version of FAT Services Booking that implements proper input validation and path sanitization on file inclusion operations, or deploy WAF rules to block directory traversal sequences in request parameters.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47693 — 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-47693 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