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

CVE-2026-2425

MEDIUM · 6.1 CVSS v3.1 Published 2026-06-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
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
The hiWeb Migration Simple plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'new_domain' parameter in all versions up to, and including, 2.0.0.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick an administrator into performing an action such as clicking on a link.

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 hiWeb Migration Simple WordPress plugin fails to sanitize the 'new_domain' parameter during input and escape it during output, allowing reflected XSS attacks. Attackers can craft malicious URLs containing JavaScript that executes when an authenticated administrator clicks the link.

MitigationUpdate the plugin to version 2.0.0.2 or later, which includes proper sanitization of the 'new_domain' parameter using WordPress sanitization functions and output escaping.

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
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 the hiWeb Migration Simple plugin is installed
    Locate the plugin directory in your WordPress installation (typically wp-content/plugins/) and verify the hiweb-migration-simple folder exists, or check via WordPress admin under Plugins > Installed Plugins
    Affected if The plugin folder 'hiweb-migration-simple' or similar variant exists in the plugins directory
  2. Identify the installed plugin version
    Open the main plugin PHP file (usually hiweb-migration-simple.php) and look for the version comment or header, or check the version field in WordPress admin plugin list
    Affected if The reported version is 2.0.0.1 or any earlier version
  3. Verify the new_domain parameter is processed
    Examine the plugin source code for handling of the 'new_domain' GET/POST parameter, typically in files handling migration or domain replacement functions
    Affected if The code processes the 'new_domain' parameter without calling sanitization functions like sanitize_text_field() or esc_html() before output
  4. Test for reflected XSS via the vulnerable parameter
    Submit a crafted request with a test payload in the new_domain parameter (e.g., ?new_domain=test"><script>alert(1)</script>) and verify if the value is reflected unescaped in the response
    Affected if The payload appears literally in the HTML output without being escaped or the script tag executes when an administrator loads the page

A user is affected if the hiWeb Migration Simple plugin version is 2.0.0.1 or earlier AND the plugin processes the 'new_domain' parameter without proper sanitization and escaping.

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 plugin to version 2.0.0.2 or later, which includes proper sanitization of the 'new_domain' parameter using WordPress sanitization functions and output escaping.

Recommended fix Moderate confidence

Latest version available on WordPress plugin repository (version > 2.0.0.1)

  1. Check the WordPress plugin repository (plugins.trac.wordpress.org) or the plugin's official page for the hiWeb Migration Simple plugin
  2. Identify the latest available version of the plugin
  3. Upgrade the plugin to the latest version available (version should be greater than 2.0.0.1)
  4. Verify the upgrade was successful
  5. Test that the 'new_domain' parameter no longer executes arbitrary scripts

Generated from the published advisory — verify against the referenced sources before acting.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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