CVE-2025-23617
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in cybio Floatbox Plus floatbox-plus allows Stored XSS.This issue affects Floatbox Plus: from n/a through <= 1.4.4.
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 Cross-Site Request Forgery (CSRF) vulnerability in Floatbox Plus versions <= 1.4.4 allows attackers to inject malicious scripts through stored XSS. Attackers can exploit this by tricking authenticated administrators into unknowingly submitting crafted requests that inject persistent malicious JavaScript into the affected site.
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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Verify Floatbox Plus installationCheck your WordPress installation for the Floatbox Plus plugin in wp-content/plugins/ and note the version number displayed in the plugins listAffected if Floatbox Plus is installed with version 1.4.4 or lower
-
Compare installed version to affected rangeReview the installed version number against the affected range (all versions <= 1.4.4)Affected if The installed version is 1.4.4 or any earlier version of Floatbox Plus
-
Confirm admin access existsVerify that administrator accounts exist and have access to the WordPress admin dashboard where Floatbox Plus settings are managedAffected if Authenticated administrator sessions are possible in this WordPress installation
-
Inspect admin forms for CSRF protectionExamine the HTML source of Floatbox Plus admin pages (typically under Settings or a dedicated Floatbox menu) and check if form submissions include CSRF tokens (look for nonce fields like wpnonce or similar token inputs)Affected if Forms lack CSRF token/nonce fields, indicating the vulnerability is present
-
Check for stored XSS in plugin settingsReview any stored data in the Floatbox Plus database tables or settings that could contain user-supplied content, and inspect the plugin code to see if admin input is properly sanitized before storage and outputAffected if Plugin settings or stored data can accept and persist unsanitized JavaScript content
A user is affected if Floatbox Plus version 1.4.4 or lower is installed and the plugin admin forms lack CSRF token protection, allowing stored XSS injection via crafted requests tricking administrators.
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 dataImplement CSRF tokens (nonces) on all admin-side forms and actions, and apply proper output encoding/sanitization to prevent XSS. Users should update to the latest patched version when available.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23617 — 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-23617 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