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

CVE-2025-14042

MEDIUM · 6.4 CVSS v3.1 Published 2026-05-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable 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 Automotive Car Dealership Business WordPress Theme for WordPress is vulnerable to Stored Cross-Site Scripting via the 'Project Details' custom field in Portfolio Items in all versions up to, and including, 13.4.1. This is due to insufficient input sanitization and output escaping on user-supplied attributes in the 'project_details' custom field. This makes it possible for authenticated attackers, with contributor-level permissions and above, 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 Automotive Car Dealership Business WordPress Theme fails to sanitize and escape user input in the 'project_details' custom field within portfolio items. Authenticated attackers with contributor-level or higher permissions can inject malicious JavaScript that executes in the browsers of users viewing affected portfolio pages.

MitigationUpdate the theme to version 13.4.2 or later if available. Until a patch is released, implement input sanitization using WordPress functions like sanitize_text_field() on the project_details field and output escaping with esc_html() or esc_attr() wherever this field is displayed.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 the theme is installed and identify its version
    In WordPress admin, go to Appearance > Themes to confirm the 'Automotive Car Dealership Business' theme is active. Check the theme version by viewing the style.css file in the theme directory or checking the theme details panel in WordPress admin.
    Affected if The installed version is lower than 13.4.2 and the theme is active.
  2. Confirm the portfolio feature is in use
    Navigate to the portfolio section in WordPress admin (typically under Portfolio or a custom post type added by the theme). Check if any portfolio entries exist that use the 'project_details' custom field.
    Affected if Portfolio entries exist and the project_details custom field is being populated with user-supplied content.
  3. Identify users with contributor-level or higher permissions
    Go to Users > All Users in WordPress admin. Review the role column to determine which users have Contributor, Author, Editor, or Administrator roles.
    Affected if Any user account with contributor-level or higher permissions exists on the site.
  4. Inspect the project_details custom field for unsanitized content
    Query the wp_postmeta table for postmeta_key = 'project_details' and examine the meta_value for any unsanitized HTML or script tags. Alternatively, edit a portfolio entry and inspect the project_details field input.
    Affected if The project_details field contains raw HTML, script tags, or event handler attributes without proper escaping.

You are affected if the Automotive Car Dealership Business theme version is below 13.4.2, the portfolio feature with project_details is in use, and contributor-level users exist on the site.

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 theme to version 13.4.2 or later if available. Until a patch is released, implement input sanitization using WordPress functions like sanitize_text_field() on the project_details field and output escaping with esc_html() or esc_attr() wherever this field is displayed.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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