VulnerabilityPublished 6 Sep 2024Updated 20 Nov 2025

CVE-2024-8509: Improper Authorization

Source CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

7.5High

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

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

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

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

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
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: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Sep 2024
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 26 Oct 2026.

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 or the CVSS exploit maturity 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

AI-suggested

To mitigate CVE-2024-8509, organizations should immediately implement strict validation of bearer tokens in the Forklift Controller system. This includes verifying token authenticity against a trusted identity provider or authorization server and enforcing proper access controls based on token scopes or claims. Network-level controls such as IP whitelisting and segmentation can reduce exposure. Monitoring and logging all authorization header usage and anomalous access patterns will help detect exploitation attempts. Until an official patch is released, consider disabling remote access to the Forklift Controller interface or placing it behind a VPN or secure gateway. Engage with the vendor or development team to obtain updates or patches addressing the authorization flaw. Conduct thorough security assessments and penetration testing focused on authentication and authorization mechanisms in the affected environment.

Description

A vulnerability was found in Forklift Controller. There is no verification against the authorization header except to ensure it uses bearer authentication. Without an Authorization header and some form of a Bearer token, a 401 error occurs. The presence of a token value provides a 200 response with the requested information.

Impact

The primary impact of CVE-2024-8509 is unauthorized disclosure of sensitive information managed by the Forklift Controller system. Attackers can bypass authentication by supplying any bearer token, allowing them to retrieve data without proper authorization. This compromises confidentiality and may expose operational details, system configurations, or other sensitive logistics data. Organizations relying on Forklift Controller for industrial automation or warehouse management could face data breaches, leading to operational disruptions, competitive disadvantage, or regulatory compliance violations. Although the vulnerability does not affect data integrity or system availability directly, the exposure of sensitive information can facilitate further attacks or espionage. The ease of exploitation and remote accessibility increase the risk of widespread abuse if the vulnerability is not mitigated promptly.

Summary

CVE-2024-8509 is an improper authorization vulnerability identified in the Forklift Controller software. The core issue lies in the authorization mechanism where the system only verifies that the Authorization header contains a bearer token format but does not validate the token's legitimacy or permissions. If the Authorization header is missing or lacks a bearer token, the system responds with a 401 Unauthorized error. However, if any bearer token is present, regardless of its validity, the system returns a 200 OK response along with the requested information. This means an attacker can craft requests with arbitrary bearer tokens and gain unauthorized access to sensitive data without needing valid credentials or authentication. The vulnerability is remotely exploitable over the network without requiring user interaction or privileges. The CVSS v3.1 score is 7.5, reflecting high severity due to the ease of exploitation and the confidentiality impact. No integrity or availability impact is noted. No patches or mitigations have been officially released yet, and no known exploits have been reported in the wild. The vulnerability affects version 0 of Forklift Controller, which may indicate an initial or early release version. The improper authorization flaw can lead to data leakage and potential exposure of sensitive operational information managed by the Forklift Controller system.

References

Community reviews

Loading reviews…