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

CVE-2026-54192

HIGH · 7.1 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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
Unauthenticated Cross Site Scripting (XSS) in Popup box <= 6.2.9 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

Unauthenticated Cross Site Scripting (XSS) vulnerability in the Popup box plugin affecting versions 6.2.9 and below. An attacker without authentication can inject malicious JavaScript code through the popup functionality, which executes in victim browsers when they interact with the crafted popup.

MitigationUpdate the Popup box plugin to a version newer than 6.2.9 once patches are available. Until then, restrict access to the affected endpoint or disable the plugin if possible.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify if Popup box plugin is installed
    Check your CMS/plugin list for the Popup box plugin. In WordPress, go to Plugins > Installed Plugins and look for 'Popup box' or similar. In other CMS, check the plugins/modules directory.
    Affected if The plugin is present in the installation
  2. Determine installed version
    View the plugin details page (in WordPress: click on the plugin name in the Plugins list) to see the version number. Compare this to 6.2.9.
    Affected if Version is 6.2.9 or lower
  3. Verify popup functionality is enabled
    Check the plugin settings/configuration panel to confirm that popup creation or display features are turned on. Look for any enabled/disabled toggle states.
    Affected if Popup functionality is enabled in the plugin settings
  4. Check if unauthenticated access is possible
    Visit your site as a logged-out visitor and determine if any popup shortcode, widget, or endpoint is publicly accessible. Check the plugin settings for any visibility or access control options.
    Affected if Popups can be triggered or displayed without authentication

If the Popup box plugin is installed at version 6.2.9 or below and the popup functionality is accessible to unauthenticated users, the environment is affected by this XSS vulnerability.

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 Popup box plugin to a version newer than 6.2.9 once patches are available. Until then, restrict access to the affected endpoint or disable the plugin if possible.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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