CVE-2025-23694
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 shabboscommerce Shabbos and Yom Tov shabbos-and-yom-tov allows Stored XSS.This issue affects Shabbos and Yom Tov: from n/a through <= 1.9.
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 CSRF vulnerability in the Shabbos and Yom Tov WordPress plugin allows authenticated attackers to inject malicious scripts via stored XSS. The lack of proper CSRF token validation on sensitive actions enables attackers to trick administrators into unknowingly submitting requests that store malicious JavaScript in the application, which then executes when other users view the compromised content.
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.
-
Identify if Shabbos and Yom Tov plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Shabbos and Yom Tov' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'shabbos-and-yom-tov' or similar.Affected if the plugin is present in the WordPress installation
-
Check the installed plugin versionIn WordPress admin, click on the plugin from the installed plugins list to view its details, or inspect the plugin's main PHP file header for the 'Version' comment.Affected if the version cannot be determined or differs from the latest patched version (version comparison required)
-
Verify plugin is activeIn WordPress admin > Plugins > Installed Plugins, confirm the Shabbos and Yom Tov plugin shows as 'Active'.Affected if the plugin is activated and in use
-
Determine if admin can be trickedThe vulnerability requires social engineering of an authenticated administrator. There is no direct configuration check; the flaw exists in the code's missing CSRF token validation on forms/AJAX actions.Affected if the plugin handles user-submitted data without anti-CSRF nonce validation on sensitive actions
A user is affected if the Shabbos and Yom Tov plugin is installed, active, and the version lacks CSRF protection on forms that store data, allowing stored XSS via tricked admin requests.
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 (nonces) on all forms and AJAX endpoints, validate Origin/Referer headers server-side, and ensure all stored data is properly sanitized before output to prevent XSS execution.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23694 — 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-23694 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