CVE-2026-27425
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 · uneditedUnauthenticated Cross Site Scripting (XSS) in Automotive Listings <= 18.6 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 confidenceUnauthenticated Cross Site Scripting (XSS) vulnerability in the Automotive Listings WordPress plugin affecting versions 18.6 and below. Attackers can inject malicious JavaScript through unsanitized input without requiring authentication.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify Automotive Listings plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Automotive Listings' in the list. Alternatively, check the /wp-content/plugins/ directory for the automotive-listings folder.Affected if The plugin is present in the WordPress installation
-
Check the installed plugin versionIn WordPress admin Plugins page, click on the plugin name to view details and find the version number. Or open the main plugin file (automotive-listings.php) and look for the 'Version' header in the plugin comments.Affected if The displayed version is 18.6 or any version lower than 18.6
-
Confirm the plugin is activeIn WordPress admin Plugins page, verify that Automotive Listings shows as 'Active' rather than 'Inactive'.Affected if The plugin is activated and running on the site
-
Identify user input entry pointsFrontend forms that accept user input and are handled by the Automotive Listings plugin (such as vehicle inquiry forms, contact forms, or submission forms) are potential XSS vectors. Visit public-facing pages using the plugin and inspect form fields.Affected if User-supplied data is being processed by the plugin without sanitization
The environment is affected if the Automotive Listings plugin is installed, active, and running version 18.6 or below.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate Automotive Listings plugin to a version newer than 18.6, or implement proper input sanitization and output encoding for all user-supplied data.
Automotive Listings version 18.7 or later
- Check the current version of the Automotive Listings plugin installed on your WordPress site
- If the installed version is 18.6 or lower, navigate to Dashboard > Plugins > Automotive Listings
- Click 'Update now' if an update is available, or manually download the latest version from the official WordPress plugin repository
- After updating, verify the plugin version is newer than 18.6
- Clear any caching plugins and server-side caches to ensure the patched version is served
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27425 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-27425 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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