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

CVE-2026-57618

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 8 weeks old

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
Contributor Cross Site Scripting (XSS) in Neve PRO <= 3.1.2 versions.

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

Cross-Site Scripting (XSS) vulnerability in Neve PRO WordPress theme/plugin affecting versions 3.1.2 and below. A user with Contributor-level privileges can inject malicious scripts (likely stored XSS) that execute when other users view the compromised content.

MitigationUpdate Neve PRO to the latest patched version. Until patched, review user permissions and consider restricting Contributor-level access to untrusted users.

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Check Neve PRO version via WordPress admin
    Navigate to WordPress admin > Plugins (or Appearance > Themes for theme mode) > locate Neve PRO and view the version number displayed
    Affected if Version displayed is 3.1.2 or lower
  2. Check Neve PRO version via plugin/theme file header
    Access the main Neve PRO plugin file (typically wp-content/plugins/neve-pro-addon/) or theme directory and open the main PHP file to find the 'Version:' comment header
    Affected if Version comment shows 3.1.2 or lower
  3. Identify Contributor-level user accounts
    In WordPress admin, go to Users > All Users and review the role column for any users assigned the Contributor role
    Affected if At least one user with Contributor role exists on the site
  4. Verify Neve PRO is active
    Confirm the Neve PRO add-on or theme is currently active on the WordPress site via Plugins or Themes admin page
    Affected if Neve PRO is active and version is 3.1.2 or below with Contributor users present

User is affected if Neve PRO version is 3.1.2 or below AND the site has active Contributor-level users who could inject stored XSS into content.

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 Neve PRO to the latest patched version. Until patched, review user permissions and consider restricting Contributor-level access to untrusted users.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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