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

CVE-2026-5070

MEDIUM · 6.4 CVSS v3.1 Published 2026-04-16
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 Vantage theme for WordPress is vulnerable to Stored Cross-Site Scripting via Gallery block text content in versions up to, and including, 1.20.32 due to insufficient output escaping in the gallery template. 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 Vantage WordPress theme contains a stored XSS vulnerability in its gallery template. Authenticated attackers with contributor-level permissions can inject arbitrary JavaScript through gallery block text content due to insufficient output escaping. The malicious script executes whenever users view pages containing the injected gallery.

MitigationUpdate the Vantage theme to version 1.20.33 or later where the vulnerability is patched. If immediate update is not possible, add proper output escaping (esc_html(), esc_attr(), or similar WordPress escaping functions) to all user-supplied content in the gallery template.

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. Confirm Vantage theme is active
    Go to WordPress admin dashboard > Appearance > Themes and verify the Vantage theme is installed and activated
    Affected if Vantage theme is the active theme
  2. Check installed Vantage theme version
    In WordPress admin, go to Appearance > Themes, click on the Vantage theme details, and note the version number displayed. Compare it to the affected range: versions prior to 1.20.33 are vulnerable
    Affected if Installed version is lower than 1.20.33
  3. Identify gallery template usage
    Check your WordPress site for pages or posts that use the Vantage gallery template or gallery block. Look for templates named 'gallery.php' or content blocks containing gallery elements in the theme folder
    Affected if The gallery template or gallery block is in use on the site
  4. Inspect gallery template for escaping
    Access the theme files via FTP or file manager. Navigate to the Vantage theme directory and locate the gallery template file (commonly templates/gallery.php or similar). Open it and search for instances where user-supplied content is output without esc_html(), esc_attr(), or similar WordPress escaping functions
    Affected if User-supplied gallery text content is output without proper escaping functions
  5. Verify contributor-level user accounts exist
    In WordPress admin, go to Users > All Users and check if any accounts with 'Contributor' role exist. These users have permission to create gallery content
    Affected if Contributor or higher-privileged user accounts exist on the site

You are affected if the Vantage theme version is below 1.20.33, the gallery template or block is in use, and contributor-level users can create or edit gallery content on your site.

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 Vantage theme to version 1.20.33 or later where the vulnerability is patched. If immediate update is not possible, add proper output escaping (esc_html(), esc_attr(), or similar WordPress escaping functions) to all user-supplied content in the gallery template.

Recommended fix High confidence

Vantage theme version 1.20.33 or later

  1. 1. Log in to the WordPress admin dashboard with administrator privileges
  2. 2. Navigate to Appearance > Themes
  3. 3. Locate the Vantage theme in the installed themes list
  4. 4. Click on the Vantage theme to view its details
  5. 5. If an update is available, click 'Update Now' to upgrade to the latest version (1.20.33 or higher)
  6. 6. Alternatively, download the latest Vantage theme version from a trusted source (official WordPress theme repository) and upload it via Appearance > Themes > Add New > Upload Theme
  7. 7. After updating, verify the version number reflects 1.20.33 or newer
  8. 8. Test the gallery functionality to ensure the patch is working 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 / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

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