CVE-2025-47583
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 Dimitri Grassi Salon booking system salon-booking-system allows Cross Site Request Forgery.This issue affects Salon booking system: from n/a through <= 10.16.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the Salon booking system plugin allows attackers to trick authenticated users into unknowingly executing unwanted state-changing actions (such as modifying bookings or user data). The lack of anti-CSRF token validation on sensitive endpoints enables malicious crafted requests to be processed by the server.
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
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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.
-
Confirm Salon booking system plugin is installedLocate the plugin in your CMS/plugin directory or check the admin panel under installed plugins. Note the installed version number.Affected if The Salon booking system plugin is installed and running without a version that includes CSRF protection.
-
Inspect forms for anti-CSRF token fieldsView the HTML source of booking forms, user management forms, and administrative forms provided by the plugin. Look for hidden input fields containing nonce values or CSRF tokens (commonly named _wpnonce, csrf_token, nonce, or similar).Affected if State-changing forms (create booking, edit booking, modify user data) lack hidden CSRF token/nonce fields in their HTML.
-
Verify AJAX endpoint CSRF protectionExamine the plugin's AJAX handlers (typically in files under /includes/ajax.php or similar). Check if each handler calls a nonce verification function before processing state-changing requests.Affected if AJAX endpoints that modify bookings or user data do not validate CSRF tokens/nonces before executing.
-
Check session cookie SameSite attributeInspect the session or authentication cookies set by the plugin or your CMS. Verify if the SameSite attribute is configured (should be set to Lax or Strict).Affected if Session cookies are missing the SameSite attribute or have it set to None without Secure flag.
You are affected if the Salon booking system plugin is installed and any of its forms, AJAX endpoints, or session cookies lack CSRF protection mechanisms.
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 anti-CSRF tokens for all state-changing operations (forms and AJAX endpoints) and configure SameSite attributes on session cookies to prevent cross-origin request forgery.
- 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-47583 — 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-47583 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