Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-54814 – Local File Inclusion (LFI) – StylemixThemes Motors WordPress Plugin up to 1.4.109

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-54814 is a high-severity PHP Local File Inclusion (LFI) vulnerability in the StylemixThemes Motors WordPress plugin, affecting all versions up to and including 1.4.109. The flaw stems from improper control of filenames used in PHP include/require statements (CWE-98), and is exploitable by unauthenticated remote attackers under specific server conditions. The vulnerability carries a CVSS v3.1 score of 8.1 (HIGH), with Confidentiality, Integrity, and Availability all rated HIGH.

Technical details

  • Root cause: The plugin fails to properly sanitize or validate user-supplied input before passing it to PHP include/require statements, classified under CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program). This allows an attacker to manipulate the filename parameter to reference arbitrary files on the server’s filesystem.

  • Trigger conditions: Exploitable remotely over the network with no user interaction required; Attack Complexity is rated HIGH (AC:H), indicating that specific non-default server conditions or configurations must be present for successful exploitation.

  • Attack vector: Network-accessible (AV:N); no authentication or user interaction required.

  • Impact: Successful exploitation can allow an attacker to read arbitrary local files from the server — including sensitive configuration files such as wp-config.php, which contains database credentials — potentially enabling complete database compromise. In certain conditions, LFI can further be chained into Remote Code Execution (RCE) through techniques such as log poisoning or inclusion of previously uploaded malicious files.

Affected software

  • StylemixThemes Motors WordPress Plugin (motors-car-dealership-classified-listings): all versions up to and including 1.4.109

Severity

  • CVSS v3.1 Base Score: 8.1 (HIGH)

  • Vector string: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Update the Motors plugin to version 1.4.110 or later, which contains the vendor-provided security fix.

  • If immediate patching is not possible, consider temporarily disabling the Motors plugin or restricting external access to the affected WordPress installation until the update can be applied.

  • Review server-side PHP error and access logs for any unusual file inclusion activity or attempts to access sensitive files such as wp-config.php.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge