dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2025-9207

MEDIUM · 5.3 CVSS v3.1 Published 2025-12-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 TI WooCommerce Wishlist plugin for WordPress is vulnerable to HTML Injection in all versions up to, and including, 2.10.0. This is due to the plugin accepting hidden fields and not limiting the values or data that can input and is later output. This makes it possible for unauthenticated attackers to inject arbitrary HTML into wishlist items.

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 TI WooCommerce Wishlist plugin for WordPress versions up to 2.10.0 is vulnerable to HTML Injection. The plugin accepts hidden fields without validating or sanitizing input values, allowing unauthenticated attackers to inject arbitrary HTML into wishlist items. When these items are displayed, the injected HTML is rendered in the browser.

MitigationUpdate the TI WooCommerce Wishlist plugin to a version beyond 2.10.0, or implement proper input validation and output encoding on all hidden field inputs to prevent HTML injection.

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
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Verify TI WooCommerce Wishlist plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'TI WooCommerce Wishlist' in the list. Note the installed version number displayed next to the plugin name.
    Affected if The plugin is listed and active with a version number at or below 2.10.0
  2. Confirm the installed version against affected range
    Compare the installed version number to the affected range. The plugin is vulnerable in any version up to and including 2.10.0. Check the plugin changelog or readme.txt file in wp-content/plugins/ti-woocommerce-wishlist for the exact version.
    Affected if Installed version is 2.10.0 or lower (for example: 2.9.0, 2.8.0, 2.7.2, etc.)
  3. Verify wishlist functionality is enabled
    Check if the wishlist feature is active on the site. Visit the frontend where the wishlist button should appear on products. Try adding a product to the wishlist as a visitor (unauthenticated). Confirm the wishlist page is accessible at the configured URL (default: /wishlist).
    Affected if Wishlist is enabled and accessible to unauthenticated visitors, allowing them to add items and view their wishlist
  4. Inspect wishlist page for rendered HTML
    Add a test product to the wishlist, then view the wishlist page in a browser. Use browser developer tools (F12) to inspect the HTML source of the wishlist items. Look for hidden form fields within wishlist item elements.
    Affected if Wishlist items render with hidden fields that contain unsanitized user-supplied values

The environment is affected if TI WooCommerce Wishlist plugin version 2.10.0 or lower is installed, active, and the wishlist feature is accessible to users who can add items that then render with unsanitized HTML content.

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 TI WooCommerce Wishlist plugin to a version beyond 2.10.0, or implement proper input validation and output encoding on all hidden field inputs to prevent HTML injection.

Recommended fix Moderate confidence

TI WooCommerce Wishlist version 2.10.1 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the TI WooCommerce Wishlist plugin
  4. Check if the current version is 2.10.0 or earlier
  5. If vulnerable, click Update Now or select the plugin and choose Update from the bulk actions menu
  6. Verify the plugin has been updated to version 2.10.1 or later
  7. Test wishlist functionality to ensure the update did not break existing features
Caveat Point release upgrade - minimal risk of breaking changes expected

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

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-2025-9207 — 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-2025-9207 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