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

CVE-2026-13114

HIGH · 7.2 CVSS v3.1 Published 2026-07-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges Zero-click 6 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
The Motors – Car Dealership & Classified Listings Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Content and User Biographical Info in all versions up to, and including, 1.4.112 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 Motors WordPress plugin fails to properly sanitize comment content and user biographical info before outputting them, allowing unauthenticated attackers to inject malicious JavaScript. This stored XSS executes whenever users view affected pages.

MitigationUpdate the plugin to a version beyond 1.4.112 that includes proper input sanitization (e.g., sanitize_text_field) and output escaping (e.g., esc_html, esc_attr) for comment content and user biographical info fields.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Verify Motors plugin is installed and active
    Log into WordPress admin, go to Plugins > Installed Plugins, and look for 'Motors' in the list. Check that it shows as 'Active'. Alternatively, check if /wp-content/plugins/motors exists on the server.
    Affected if The Motors plugin is installed and active in WordPress.
  2. Check installed plugin version
    In WordPress admin > Plugins > Installed Plugins, click on 'Motors' to view the plugin details, or open /wp-content/plugins/motors/motors.php and look for the 'Version:' header in the plugin comment block.
    Affected if The installed version is 1.4.112 or earlier.
  3. Inspect comment content for injected scripts
    Go to WordPress admin > Comments. Look for any comments on posts (especially car listings, inventory, or custom post types created by Motors). View the raw comment content - check for <script> tags, javascript: URLs, onmouseover/onerror attributes, or encoded payloads.
    Affected if Any comment contains unsanitized HTML or JavaScript that would execute when viewed.
  4. Review user biographical info fields
    Go to WordPress admin > Users > Profile (or Users > All Users > Edit for a specific user). Check the 'Biographical Info' or 'Bio' field for any HTML tags, script elements, or event handlers.
    Affected if The user biographical info field contains raw, unescaped HTML or JavaScript.
  5. Check for unescaped output in Motors templates
    View the source code of a Motors-powered page (car listing, inventory page). Right-click > View Page Source. Search for the comment content or user bio as it appears on the page - verify that special characters like < > " are converted to HTML entities.
    Affected if Output appears as raw HTML without entity encoding (e.g., <script> appears literally in the page source rather than as &lt;script&gt;).

A user is affected if the Motors plugin version is 1.4.112 or earlier AND the site accepts comments or has users with biographical info that could contain unsanitized scripts.

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 plugin to a version beyond 1.4.112 that includes proper input sanitization (e.g., sanitize_text_field) and output escaping (e.g., esc_html, esc_attr) for comment content and user biographical info fields.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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