CVE-2026-1835VulnerabilityPublished 4 Feb 2026Updated 23 Feb 2026

CVE-2026-1835: lcg0124 BootDo · Cross-Site Request Forgery

Affects lcg0124 BootDoSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.3Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, 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: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Feb 2026
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
lcg0124BootDo	Affected =e93dd428ef6f5c881aa74d49a2099ab0cf1e0fcb	Fixed in–

AI-suggested

To mitigate CVE-2026-1835, organizations should implement robust anti-CSRF protections such as synchronizer tokens or double-submit cookies in all state-changing HTTP requests. Review and update BootDo deployments to the latest available releases, as the rolling release strategy may have introduced patches after the identified commit. Employ strict Content Security Policy (CSP) headers to reduce the risk of malicious script execution that could facilitate CSRF attacks. Educate users about the risks of clicking untrusted links or visiting suspicious websites while authenticated. Use web application firewalls (WAFs) with CSRF detection capabilities to block suspicious requests. Conduct regular security assessments and code reviews focusing on CSRF protections in custom or integrated components. Monitor public vulnerability databases and vendor advisories for updates or patches. If immediate patching is not feasible, consider restricting access to BootDo management interfaces via network segmentation or VPNs to reduce exposure. Logging and alerting on unusual user actions can help detect potential exploitation attempts.

Description

A vulnerability was identified in lcg0124 BootDo up to e93dd428ef6f5c881aa74d49a2099ab0cf1e0fcb. This affects an unknown part. The manipulation leads to cross-site request forgery. The attack is possible to be carried out remotely. The exploit is publicly available and might be used. This product adopts a rolling release strategy to maintain continuous delivery. Therefore, version details for affected or updated releases cannot be specified.

Impact

The primary impact of CVE-2026-1835 is on the integrity of affected systems, as attackers can trick authenticated users into performing unauthorized actions, potentially altering data or application state without consent. Confidentiality and availability impacts are minimal or none. The ease of exploitation is moderate since it requires user interaction but no authentication or privileges. The presence of a public exploit increases the risk of exploitation, especially in environments where users have elevated permissions. Organizations worldwide using BootDo in web-facing applications could face unauthorized configuration changes, data manipulation, or other integrity violations. This could lead to operational disruptions, loss of trust, or compliance issues. The rolling release model means some users may unknowingly run vulnerable versions, complicating patch management. While no widespread exploitation is reported, the availability of an exploit and the remote attack vector make this a credible threat that requires timely mitigation.

Summary

CVE-2026-1835 identifies a Cross-Site Request Forgery (CSRF) vulnerability in the lcg0124 BootDo product up to the commit e93dd428ef6f5c881aa74d49a2099ab0cf1e0fcb. CSRF vulnerabilities allow attackers to induce authenticated users to submit forged HTTP requests unknowingly, potentially causing unauthorized state-changing actions on web applications. This vulnerability is exploitable remotely without requiring attacker authentication or privileges, but it does require user interaction, such as clicking a malicious link or visiting a crafted webpage. The vulnerability stems from insufficient or absent CSRF token validation or other anti-CSRF mechanisms in the affected component, which is unspecified. BootDo employs a rolling release strategy, meaning continuous updates without fixed version numbers, complicating precise identification of affected or patched versions. The CVSS 4.0 vector indicates network attack vector, low attack complexity, no privileges required, user interaction needed, and limited impact on integrity with no impact on confidentiality or availability. While no confirmed exploitation in the wild is reported, a public exploit exists, increasing the likelihood of future attacks. The vulnerability could allow attackers to manipulate user actions, potentially leading to unauthorized changes in application state or data integrity issues. Given the nature of CSRF, the impact depends on the privileges of the victim user and the sensitivity of the affected operations. Organizations using BootDo should assess their exposure, implement CSRF protections, and monitor for updates due to the rolling release model.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 21:58 UTC

Technical details

References

Community reviews

Related threats