CVE-2025-32654
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 · moderate confidenceA PHP Local File Inclusion (LFI) vulnerability exists in the Motors WordPress plugin (car dealership classified listings) due to improper control of filenames in include/require statements. An attacker could potentially read sensitive local files on the server by manipulating file path parameters.
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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/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.
-
Verify Motors plugin installationNavigate to WordPress admin dashboard > Plugins. Locate the Motors plugin in the list and note the installed version number displayed under the plugin name.Affected if The Motors plugin is installed and the version is 1.4.71 or lower (or if the version cannot be determined).
-
Check plugin version via file systemAccess the WordPress installation via FTP or file manager. Navigate to wp-content/plugins/motors/ and open the main plugin file (typically motors.php or index.php). Look for the version definition in the plugin header comments.Affected if The version returned is 1.4.71 or lower, or the version cannot be verified.
-
Identify file inclusion endpointsSearch the plugin source code for include, require, include_once, or require_once statements that use variables in the path. Examine files in the plugin directory that handle user requests (e.g., AJAX handlers, shortcode callbacks, template files).Affected if File inclusion functions using dynamic variable paths are found in the plugin code.
-
Verify parameter accessibilityExamine the identified inclusion code to determine if the path parameter originates from user input (GET, POST, or REQUEST superglobals). Test by accessing suspected endpoints with traversal patterns (e.g., ../../../../etc/passwd) to confirm parameter acceptance.Affected if User-controlled input flows directly to file inclusion functions without sanitization.
-
Review server access logsCheck web server access logs (Apache/nginx) for suspicious requests to WordPress endpoints containing directory traversal sequences (../) in parameters used by the Motors plugin.Affected if Logs show requests with traversal patterns targeting Motors plugin parameters.
If the Motors plugin is installed at version 1.4.71 or lower and uses user input in file inclusion functions without validation, the environment is affected by this LFI vulnerability.
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 dataUpdate the Motors plugin to a version beyond 1.4.71, or implement strict input validation and path sanitization on any user-controlled file inclusion parameters to prevent directory traversal attacks.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32654 — 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-32654 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