CVE-2025-8321VulnerabilityPublished 30 Jul 2025

CVE-2025-8321: Tesla Wall Connector · Security Version Number Mutable to Older Versions

Affects Tesla Wall ConnectorSource CVE Database V5

Not known to be exploited · CVSS 6.8 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.0 base score

6.8Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector: Physical
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Physical: The attack requires the attacker to physically touch or manipulate the vulnerable component. Physical interaction may be brief or persistent.
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Tesla Wall Connector	Affected =24.44.1	Fixed in–

AI-suggested

To mitigate this vulnerability, European organizations should implement the following specific measures: 1) Physically secure Tesla Wall Connectors to restrict unauthorized access, including installing them in locked enclosures or monitored areas. 2) Monitor firmware versions actively and verify that devices are running the latest firmware releases from Tesla, as newer versions may include patches or improved security controls. 3) Tesla and integrators should prioritize developing and deploying firmware updates that incorporate anti-downgrade protections to prevent reversion to vulnerable versions. 4) Implement network segmentation and strict access controls for networks connected to Wall Connectors to limit lateral movement in case of device compromise. 5) Employ tamper detection mechanisms and regular physical inspections to detect unauthorized access attempts. 6) Maintain logs and alerts for unusual device behavior or firmware changes. 7) Engage with Tesla support channels to stay informed about patches and advisories. 8) For organizations managing multiple Wall Connectors, consider deploying centralized management solutions that can enforce firmware integrity and provide real-time status monitoring. These steps go beyond generic advice by focusing on physical security, firmware integrity verification, and network isolation tailored to the operational context of EV charging infrastructure.

Description

Tesla Wall Connector Firmware Downgrade Vulnerability. This vulnerability allows physically present attackers to execute arbitrary code on affected installations of Tesla Wall Connector devices. Authentication is not required to exploit this vulnerability. The specific flaw exists within the firmware upgrade feature. The issue results from the lack of an anti-downgrade mechanism. An attacker can leverage this in conjunction with other vulnerabilities to execute code in the context of the device. Was ZDI-CAN-26299.

Impact

For European organizations, the impact of this vulnerability can be substantial, especially for entities operating fleets of Tesla vehicles or managing EV charging infrastructure. Compromise of Wall Connectors could lead to denial of charging services, impacting operational continuity for businesses relying on electric vehicles. Additionally, arbitrary code execution on these devices could be used to pivot into internal networks, potentially exposing sensitive corporate data or disrupting other connected systems. Given the physical access requirement, the threat is more pronounced in locations where devices are accessible to unauthorized personnel, such as public or semi-public charging stations. The high impact on confidentiality, integrity, and availability means attackers could manipulate charging data, disable devices, or use the compromised Wall Connector as a launchpad for further attacks. This could also affect smart grid integrations and energy management systems that interface with these devices, amplifying the potential disruption. The vulnerability may also undermine user trust in EV infrastructure security, which is critical for the ongoing transition to electric mobility in Europe.

CWE-1328Security Version Number Mutable to Older Versions (opens in a new tab)
Base weakness
Security-version number in hardware is mutable, resulting in the ability to downgrade (roll-back) the boot firmware to vulnerable code versions.
Architecture and Design
When architecting the system, security version data should be designated for storage in registers that are either read-only or have access controls that prevent modification by an untrusted agent.
Implementation
During implementation and test, security version data should be demonstrated to be read-only and access controls should be validated.
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
Attack patterns
Configuration/Environment Manipulation (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

zerodayinitiative.com/advisories/ZDI-25-712/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Jul 2025, 01:33 UTC

WeaknessesCWE-1328

Technical details

References

Community reviews

Related threats