CVE-2025-32142
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 · uneditedImproper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Stylemix Motors motors-car-dealership-classified-listings allows PHP Local File Inclusion.This issue affects Motors: from n/a through <= 1.4.71.
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 confidenceA PHP Local File Inclusion (LFI) vulnerability exists in the Motors WordPress plugin (motors-car-dealership-classified-listings) where user-controlled input is improperly used in PHP include/require statements without sufficient validation. This allows attackers to read sensitive local files via path traversal, potentially exposing configuration files, credentials, or other sensitive data.
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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Identify if Motors plugin is installedIn WordPress admin, navigate to Plugins > Installed Plugins and look for 'Motors - Car Dealership & Classified Listings', or check the /wp-content/plugins/ directory for the motors-car-dealership-classified-listings folderAffected if The Motors plugin is present in the WordPress installation
-
Determine the installed Motors plugin versionIn WordPress admin, go to Plugins > Installed Plugins and click on the Motors plugin to view its version number, or check the main plugin file (e.g., index.php or motors.php) for the 'Version' header commentAffected if The installed version is lower than 1.4.72 (versions prior to 1.4.72 are affected)
-
Identify accessible endpoints that may process file inclusion parametersReview the site for URLs that include query parameters potentially used for file inclusion (common patterns include 'template', 'file', 'path', 'page', 'view', or 'include' in the URL query string). Check public-facing templates that handle these parameters.Affected if The site uses URL parameters to include PHP files without proper validation, and the plugin version is below 1.4.72
-
Test for path traversal vulnerabilityIf a file inclusion parameter is identified, test by appending path traversal sequences (e.g., ../../../../wp-config.php) to the parameter value in a request and observe if the file content is returned or if the application attempts to include the fileAffected if The application returns file contents or includes files outside the intended directory, indicating the LFI vulnerability is present
The environment is affected if the Motors plugin version is below 1.4.72 AND the vulnerable file inclusion parameter is accessible and allows path traversal to read arbitrary local files.
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.
From vendor dataUpgrade the Motors plugin to version 1.4.72 or later. If immediate patching is not possible, implement web application firewall (WAF) rules to block path traversal patterns (e.g., ../../) and restrict include/require statements to allowlisted paths.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32142 — 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-2025-32142 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