CVE-2025-39355
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 Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in roninwp FAT Services Booking fat-services-booking allows SQL Injection.This issue affects FAT Services Booking: from n/a through <= 5.6.
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 confidenceSQL injection vulnerability in the FAT Services Booking WordPress plugin allows attackers to inject malicious SQL commands via unsanitized user inputs in SQL queries. With a CVSS of 8.5 (HIGH), successful exploitation could enable unauthorized database access, data exfiltration, or data manipulation.
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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L
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 FAT Services Booking plugin is installedNavigate to WordPress admin > Plugins and check if 'FAT Services Booking' appears in the installed plugins list, or inspect the directory wp-content/plugins/ for a folder named 'fat-services-booking'Affected if The plugin is present in the WordPress installation
-
Identify the installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins > FAT Services Booking and read the version number from the plugin details, or open the main plugin PHP file (usually fat-services-booking.php) and check the 'Version' header in the plugin comment blockAffected if The version number is 5.6 or lower
-
Verify the plugin is activeIn WordPress admin > Plugins, confirm the FAT Services Booking plugin shows as 'Active' rather than 'Inactive'Affected if The plugin is currently active and handling requests
-
Check if user-facing forms existInspect the frontend of the WordPress site for any booking forms, service request forms, or other input forms created by the FAT Services Booking pluginAffected if The plugin exposes user input forms that could submit data to unauthenticated SQL query endpoints
-
Determine if unauthenticated access is possibleTest whether the vulnerable SQL endpoints can be reached without authentication by examining the plugin's AJAX handlers or public-facing query parameters (check for actions like 'fat_sb_' prefixes in request parameters)Affected if The plugin accepts user input via GET/POST parameters without requiring authentication
If FAT Services Booking plugin is installed, active, version 5.6 or lower, and exposes user input fields or endpoints, the environment is affected by this SQL injection 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 dataUpgrade to a patched version of FAT Services Booking (>5.6) that implements proper input sanitization and uses parameterized queries/prepared statements for all database interactions.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-39355 — 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-39355 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