EUVD-2025-209982
GHSA-64cg-w47x-76fj
Severity by source
AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
Primary rating from Vendor (Wordfence) · only source for this CVE.
CVSS VectorVendor: Wordfence
Lifecycle Timeline
2DescriptionCVE.org
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.
AnalysisAI
Stored Cross-Site Scripting in the Automotive Car Dealership Business WordPress Theme (all versions through 13.4.1) enables authenticated contributors to permanently embed arbitrary JavaScript via the 'project_details' custom field in Portfolio Items. Because the CVSS scope is Changed (S:C), injected scripts execute in the victim's browser context - not just the WordPress admin panel - enabling session hijacking, credential harvesting, or drive-by malware delivery against site visitors. No public exploit code has been identified at time of analysis, though contributor-level access is routinely available in multi-author dealership or agency WordPress deployments, making the authentication barrier practically low.
Technical ContextAI
The vulnerability resides in a custom field ('project_details') associated with Portfolio Items - a custom post type registered by the ThemeSuite Automotive Car Dealership Business WordPress Theme (CPE: cpe:2.3:a:themesuite:automotive_car_dealership_business_wordpress_theme:*). CWE-79 (Improper Neutralization of Input During Web Page Generation) identifies the root cause: user-supplied attribute data in the custom field is neither sanitized on input nor escaped on output, allowing raw HTML/JavaScript to persist in the database and render in page responses. The Changed scope in the CVSS vector (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N) confirms the injected payload crosses the WordPress application boundary into the victim browser's security context, which is characteristic of Stored XSS where the vulnerable component (WordPress backend) differs from the impacted component (end-user browser session).
RemediationAI
No specific patched version number was included in the available intelligence data - patch availability should be confirmed directly via the ThemeForest item page (https://themeforest.net/item/automotive-car-dealership-business-wordpress-theme/9210971) and the Wordfence advisory (https://www.wordfence.com/threat-intel/vulnerabilities/id/ced350cf-1116-4003-ac74-f6dec34360a5). Site administrators should update the theme to the latest available version immediately and verify the changelog addresses CVE-2025-14042. As a compensating control pending patch deployment, restrict contributor-level role assignments to fully trusted users only and audit existing contributor accounts for unauthorized additions - this directly removes the PR:L prerequisite. Disabling the Portfolio Items custom post type or removing the 'project_details' custom field via child theme overrides would eliminate the attack surface entirely but may break theme functionality. Additionally, a Web Application Firewall rule blocking script injection patterns in POST bodies targeting wp-admin/post.php can provide defense-in-depth with minimal operational side effects.
Same weakness CWE-79 – Cross-site Scripting (XSS)
View allShare
External POC / Exploit Code
Leaving vuln.today