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

CVE-2026-57402

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-13
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 5 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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in wpdesk Flexible Refund and Return Order for WooCommerce flexible-refund-and-return-order-for-woocommerce allows Stored XSS.This issue affects Flexible Refund and Return Order for WooCommerce: from n/a through <= 1.0.51.

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

A Stored XSS vulnerability exists in the WordPress plugin 'Flexible Refund and Return Order for WooCommerce' (versions up to 1.0.51). The plugin fails to properly sanitize user input submitted through refund/return request forms, allowing attackers to inject malicious JavaScript that executes when administrators view the stored refund requests.

MitigationUpdate to a patched version of the plugin when available. Until then, restrict access to the WooCommerce refund management backend to trusted users only, and consider deploying a WAF rule to detect XSS payloads in refund form submissions.

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 the plugin is installed and get its version
    In WordPress admin, go to Plugins > Installed Plugins, locate 'Flexible Refund and Return Order for WooCommerce', and note the version number displayed. Alternatively, check the plugin files in wp-content/plugins/flexible-refund-order-return-for-woocommerce/ for a version marker.
    Affected if The installed version is 1.0.51 or lower (the vulnerable version range)
  2. Confirm the refund request form is enabled
    Navigate to the plugin settings in WordPress admin (typically under WooCommerce > Refund Settings or a similar menu item created by the plugin). Verify that the return/refund request form is active and publicly accessible.
    Affected if The refund form is enabled and exposed on the site, creating an attack surface for XSS injection
  3. Inspect existing refund request data for malicious payloads
    Access the refund request management area in WordPress admin (usually under WooCommerce > Refund Requests or the plugin's menu). Review stored requests for any JavaScript tags, event handlers (onclick, onerror, etc.), or unusual HTML in fields such as customer name, order details, or refund reason.
    Affected if Any refund requests contain unescaped HTML or JavaScript code, indicating successful XSS injection
  4. Check admin access controls on refund management
    Review user roles and capabilities accessing the WooCommerce refund request backend. Go to Users > All Users and verify which roles can view refund requests. Ensure only trusted administrators have access.
    Affected if Multiple untrusted users or roles have permission to view refund requests in the admin panel

You are affected if the plugin version is 1.0.51 or lower AND the refund form is enabled, allowing external users to submit requests that get stored with unsanitized input viewable by admins.

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 to a patched version of the plugin when available. Until then, restrict access to the WooCommerce refund management backend to trusted users only, and consider deploying a WAF rule to detect XSS payloads in refund form submissions.

Recommended fix Moderate confidence

Latest version of Flexible Refund and Return Order for WooCommerce (version > 1.0.51)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Flexible Refund and Return Order for WooCommerce' by wpdesk
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. Alternatively, manually download the latest version from the WordPress plugin repository and reinstall
  6. 6. After updating, verify the plugin is working correctly and test that the XSS vulnerability is no longer present
Caveat Review the plugin changelog before upgrading to check for any breaking changes or functionality changes in newer versions

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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