dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-4920

MEDIUM · 6.4 CVSS v3.1 Published 2026-05-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
The Next Date plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'default' shortcode attribute in all versions up to, and including, 1.0 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 confidence

The Next Date WordPress plugin (versions up to 1.0) contains a stored XSS vulnerability in the 'default' shortcode attribute due to insufficient input sanitization and output escaping. Authenticated attackers with contributor-level access or higher can inject arbitrary JavaScript through the vulnerable attribute, which executes whenever users access affected pages.

MitigationUpdate the Next Date plugin to a patched version once available, or add proper input sanitization (e.g., sanitize_text_field) and output escaping (e.g., esc_attr, esc_html) to the 'default' shortcode attribute processing.

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
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

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 Next Date plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'next-date' or 'next-date-wordpress'. Alternatively, log into the WordPress admin panel and navigate to Plugins > Installed Plugins to look for 'Next Date' in the list.
    Affected if The plugin is not found in the plugins directory or not listed in the WordPress admin plugins page, indicating it is not installed.
  2. Determine the installed plugin version
    If the plugin is installed, open the main plugin PHP file (typically next-date.php or similar in the plugin folder) and locate the 'Version' header in the plugin comments at the top of the file. Compare this version number to the affected range (versions up to and including 1.0).
    Affected if The version number is 1.0 or lower, indicating the installation is within the affected version range.
  3. Locate shortcode usage in content
    Search the WordPress database for instances of the [next_date] shortcode by querying the wp_posts table for post content containing 'next_date' and specifically looking for the 'default' attribute (for example: [next_date default="..."]). This can be done via phpMyAdmin, WP-CLI (wp db query), or by searching post content through the WordPress admin interface.
    Affected if Any posts, pages, or custom post types contain the [next_date] shortcode with a 'default' attribute present.
  4. Verify user role permissions
    Review WordPress user roles to determine if any accounts exist with Contributor-level or higher access. Check Users > All Users in the admin panel or query the wp_usermeta table for capabilities like 'edit_posts' (Contributor) or higher roles.
    Affected if There are one or more user accounts with Contributor, Author, Editor, or Administrator roles who could potentially create or edit content containing the malicious shortcode.

You are affected if the Next Date plugin is installed with version 1.0 or lower AND the [next_date] shortcode with a 'default' attribute is present in any published content, especially when contributor-level or higher users exist who could inject the payload.

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

Update the Next Date plugin to a patched version once available, or add proper input sanitization (e.g., sanitize_text_field) and output escaping (e.g., esc_attr, esc_html) to the 'default' shortcode attribute processing.

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

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4920 — 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-2026-4920 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