CVE-2025-23690
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 ArtkanMedia Book a Place book-a-place allows Stored XSS.This issue affects Book a Place: from n/a through <= 0.7.1.
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 confidenceCSRF vulnerability in the ArtkanMedia Book a Place WordPress plugin (versions <= 0.7.1) allows attackers to craft malicious requests that inject and store XSS payloads through booking forms. An authenticated victim viewing the injected content triggers the stored XSS.
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 plugin installationIn WordPress admin, navigate to Plugins > Installed Plugins and locate 'Book a Place' by ArtkanMedia. Note the version number displayed.Affected if Plugin is installed and version is 0.7.1 or lower
-
Confirm version vulnerabilityCompare the installed version number against the affected range (0.7.1 and below). The version is typically visible in the plugin description or in the plugins directory on the filesystem under wp-content/plugins/book-a-place/Affected if Installed version is 0.7.1 or any version <= 0.7.1
-
Check booking form exposureVisit the frontend page where the booking form shortcode [book_a_place] or widget is deployed. Verify the form accepts and stores user input (name, email, date, etc.).Affected if Booking form is active and accessible to unauthenticated users
-
Inspect stored data for injected payloadsAccess the WordPress database via phpMyAdmin or WP-CLI and query the plugin's booking table (commonly wp_book_a_place or similar) for suspicious HTML/script tags in stored fields. Alternatively, check the admin booking list view for unusual content in submitted fields.Affected if Any booking records contain script tags, javascript:, or HTML event handlers in input fields
The environment is affected if the Book a Place plugin version is 0.7.1 or lower AND the booking form is actively collecting and displaying user submissions.
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 to the latest version of Book a Place if available. Until a patch is released, disable the plugin or implement additional anti-CSRF protection via web application firewall rules.
- 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-23690 — 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-23690 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