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

CVE-2026-39463

HIGH · 7.1 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 →
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 ManageWP Worker <= 4.9.31 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

An unauthenticated Cross Site Scripting (XSS) vulnerability exists in the ManageWP Worker plugin for WordPress versions 4.9.31 and below. An attacker can inject malicious scripts into the application without requiring authentication, potentially compromising other users or administrators accessing the affected functionality.

MitigationUpdate ManageWP Worker to the latest version immediately. If immediate updating is not possible, disable the plugin until a patch can be applied. Additionally, implement output encoding and input validation as a defense-in-depth measure.

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. Locate the ManageWP Worker plugin installation
    Check your WordPress site's wp-content/plugins/ directory for a folder named 'worker' or 'managewp-worker'. If using a managed WordPress host, verify through the WordPress admin dashboard under Plugins > Installed Plugins.
    Affected if The ManageWP Worker plugin is not installed on the WordPress site.
  2. Identify the installed plugin version
    Open the main plugin file (typically worker/readme.txt or worker/worker.php) and locate the 'Version:' field in the plugin header comment, or check the version listed in the WordPress admin Plugins page.
    Affected if Unable to determine the version number from plugin files.
  3. Compare the installed version to the affected range
    Compare the version number found in step 2 against 4.9.31. Versions 4.9.31 and lower are within the affected range.
    Affected if The installed version is 4.9.31 or lower (for example, 4.9.30, 4.9.0, 4.8.0, etc.).

If the ManageWP Worker plugin is installed and the version is 4.9.31 or below, the environment is affected by this unauthenticated 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 ManageWP Worker to the latest version immediately. If immediate updating is not possible, disable the plugin until a patch can be applied. Additionally, implement output encoding and input validation as a defense-in-depth measure.

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-39463 — 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-39463 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