dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-46528

HIGH · 7.1 CVSS v3.1 Published 2025-04-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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 · unedited
Cross-Site Request Forgery (CSRF) vulnerability in Steve Availability Calendar availability allows Stored XSS.This issue affects Availability Calendar: from n/a through <= 0.2.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 confidence

A CSRF vulnerability in Steve Availability Calendar plugin versions up to 0.2.4 allows authenticated users to be tricked into submitting malicious requests that inject and store XSS payloads via calendar availability entries. The lack of anti-CSRF token validation on state-changing forms enables attackers to craft malicious links that, when clicked by a logged-in administrator, permanently embed malicious scripts into the application.

MitigationImplement anti-CSRF tokens on all state-changing forms (especially availability entry forms) and apply strict input validation with output encoding to prevent stored XSS. Additionally, consider adding SameSite cookie attributes and Origin/Referer validation.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Steve Availability Calendar plugin is installed
    Navigate to WordPress admin dashboard > Plugins and look for 'Steve Availability Calendar' in the installed plugins list, or check the wp-content/plugins directory for a folder named 'steve-availability-calendar' or similar.
    Affected if The plugin is present in the WordPress installation.
  2. Determine the installed plugin version
    In WordPress admin > Plugins > Installed Plugins, find Steve Availability Calendar and read the version number from the plugin details. Alternatively, open the main plugin PHP file (e.g., steve-availability-calendar.php) and look for the 'Version' header in the plugin comment block.
    Affected if The version is 0.2.4 or any earlier version.
  3. Inspect availability entry form for anti-CSRF protection
    Navigate to the calendar availability entry form in the plugin admin interface. View the page source (right-click > View Page Source) and search for a hidden CSRF token field (commonly named 'nonce', '_wpnonce', 'csrf_token', or similar). Check if the form submission includes a token parameter.
    Affected if The form lacks a hidden anti-CSRF token field or the submitted form data does not include a validated nonce/token.
  4. Test for stored XSS in availability entries
    Submit an availability entry with a test XSS payload in a text field (e.g., <script>alert('XSS')</script>). Save the entry and then view the calendar or the admin page where entries are displayed. Inspect the HTML source of the rendered page to see if the payload is executed or appears unescaped.
    Affected if The XSS payload is executed or rendered as raw HTML without sanitization when the availability entry is displayed.
  5. Verify admin cookie SameSite attribute
    Use browser developer tools > Application tab > Cookies. Inspect the WordPress admin session cookie (usually 'wordpress_sec_') and check if the SameSite attribute is set to 'Lax' or 'Strict'. Alternatively, view raw cookie headers via the Network tab on any admin page request.
    Affected if The SameSite attribute is missing, set to 'None', or not configured, making the cookie vulnerable to being sent on cross-site malicious requests.

A user is affected if the Steve Availability Calendar plugin version 0.2.4 or earlier is installed AND the availability entry form lacks anti-CSRF token validation AND the form stores submitted input without sanitization, allowing stored XSS to persist.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens on all state-changing forms (especially availability entry forms) and apply strict input validation with output encoding to prevent stored XSS. Additionally, consider adding SameSite cookie attributes and Origin/Referer validation.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-46528 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-46528 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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