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

CVE-2026-39491

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-15
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

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
Subscriber Cross Site Scripting (XSS) in JupiterX Core <= 4.14.1 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 · high confidence

Stored Cross Site Scripting (XSS) vulnerability in JupiterX Core WordPress theme/plugin affecting versions 4.14.1 and below. Users with subscriber-level privileges (the lowest WordPress role) can inject malicious JavaScript code that gets stored and executed when viewed by higher-privileged users.

MitigationUpdate JupiterX Core to a version newer than 4.14.1 immediately. If an update is unavailable, disable the plugin or theme until a patch is released, and consider implementing a WAF rule to block XSS payloads.

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. Verify JupiterX Core is installed
    Log into WordPress admin panel and navigate to Plugins or Appearance > Themes. Look for 'JupiterX Core' in the installed plugins list or active theme details.
    Affected if JupiterX Core appears in the installed plugins or themes list
  2. Determine the installed version of JupiterX Core
    In WordPress admin, go to Plugins > Installed Plugins > JupiterX Core and read the version number displayed below the plugin name. Alternatively, check the version in the theme details if it is installed as a theme.
    Affected if The version shown is 4.14.1 or any version below 4.14.1
  3. Confirm WordPress user registration is enabled at subscriber level
    Navigate to WordPress Settings > General and check if 'Membership' is enabled with 'Anyone can register' selected, then verify if the default role for new users includes subscriber-level access.
    Affected if User registration is enabled and new users can register with subscriber role or higher privileges exist alongside subscriber accounts
  4. Check for existing subscriber-level user accounts
    Go to Users > All Users in the WordPress admin panel and review the list of users. Look for accounts with the 'Subscriber' role.
    Affected if One or more subscriber-level user accounts exist on the site

The environment is affected if JupiterX Core version 4.14.1 or below is installed AND subscriber-level user accounts exist or can be created on the WordPress 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update JupiterX Core to a version newer than 4.14.1 immediately. If an update is unavailable, disable the plugin or theme until a patch is released, and consider implementing a WAF rule to block XSS payloads.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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