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

CVE-2026-3003

HIGH · 7.2 CVSS v3.1 Published 2026-03-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges 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 Vagaro Booking Widget plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘vagaro_code’ parameter in all versions up to, and including, 0.3 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers 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 Vagaro Booking Widget plugin for WordPress versions up to 0.3 contains a stored XSS vulnerability in the vagaro_code parameter. Unauthenticated attackers can inject malicious JavaScript through insufficient input sanitization, which persists in the database and executes whenever users access affected pages due to missing output escaping.

MitigationUpdate the Vagaro Booking Widget plugin to the latest version and audit existing content for injected scripts. Until patched, consider disabling the plugin or implementing a WAF rule to filter malicious vagaro_code parameter submissions.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify Vagaro Booking Widget plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Vagaro Booking Widget' or check the plugin files in wp-content/plugins/ directory for the vagaro-booking-widget folder
    Affected if The plugin is installed and active
  2. Check installed plugin version
    In WordPress admin Plugins page, click on the plugin to view details and find the version number, or read the main plugin PHP file header which contains the Version field
    Affected if Version is 0.3 or lower (all versions up to 0.3 are affected)
  3. Inspect database for vagaro_code entries
    Query the wp_options table (or similar options table with prefix) for option_name containing 'vagaro' or look for any stored vagaro_code values: SELECT * FROM wp_options WHERE option_name LIKE '%vagaro%'
    Affected if Any vagaro_code value exists in the database options table
  4. Examine vagaro_code for malicious scripts
    Review the stored vagaro_code value(s) from the database query for suspicious characters like <script>, javascript:, onerror, onload, or other HTML/JS fragments
    Affected if The vagaro_code contains unescaped HTML tags, JavaScript event handlers, or script elements

You are affected if the Vagaro Booking Widget plugin version is 0.3 or lower AND the vagaro_code parameter is populated in your database with any user-supplied content that may contain unsanitized script tags or event handlers.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Vagaro Booking Widget plugin to the latest version and audit existing content for injected scripts. Until patched, consider disabling the plugin or implementing a WAF rule to filter malicious vagaro_code parameter submissions.

Recommended fix Moderate confidence

Vagaro Booking Widget version > 0.3

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Vagaro Booking Widget plugin
  4. If an update is available, click 'Update Now' to install the latest version (version > 0.3)
  5. Alternatively, navigate to Plugins > Add New > Upload Plugin to manually upload the fixed version if available on WordPress.org
  6. After updating, verify the plugin is active and functioning correctly

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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