CVE-2026-1835
Cross-Site Request Forgery in BootDo Enables Remote Attacks
Publication date: 2026-02-04
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| lcg0124 | bootdo | to 1.0 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-862 | The product does not perform an authorization check when an actor attempts to access a resource or perform an action. |
| CWE-352 | The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-1835 is a Cross-Site Request Forgery (CSRF) vulnerability found in the BootDo software, specifically in the UserController.java file within the save method. This method lacks proper CSRF protection, allowing attackers to trick authenticated users into performing unauthorized actions without their consent.
The vulnerability enables remote attackers to execute actions on behalf of legitimate users by sending forged requests, potentially modifying account settings, creating new administrator accounts, or accessing sensitive user data.
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized modifications of user accounts and system settings, unauthorized transactions, and exposure of sensitive user data.
Exploitation can result in breaches of user privacy, financial losses, and a loss of trust in the security and integrity of the affected application.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': "The vulnerability is a Cross-Site Request Forgery (CSRF) issue in the BootDo system, specifically in the UserController.java file's save method at the endpoint /sys/user/save. Detection involves monitoring for unauthorized or suspicious requests targeting this endpoint that could exploit the lack of CSRF protection."}, {'type': 'paragraph', 'content': 'Since the vulnerability allows attackers to perform unauthorized actions remotely without authentication but requires user interaction, detection can include analyzing web server logs for unexpected POST requests to /sys/user/save, especially those lacking valid CSRF tokens.'}, {'type': 'paragraph', 'content': 'Suggested commands to detect potential exploitation attempts include using tools like curl or grep on server logs to identify suspicious requests:'}, {'type': 'list_item', 'content': "grep 'POST /sys/user/save' /var/log/nginx/access.log"}, {'type': 'list_item', 'content': "grep 'POST /sys/user/save' /var/log/httpd/access_log"}, {'type': 'list_item', 'content': "curl -v -X POST https://your-bootdo-instance/sys/user/save --header 'Content-Type: application/x-www-form-urlencoded' --data 'malicious_payload_here' (for testing in a controlled environment)"}, {'type': 'paragraph', 'content': 'Additionally, reviewing the application source code or runtime behavior to confirm the absence of CSRF tokens or protection mechanisms on the /sys/user/save endpoint can help detect the vulnerability.'}] [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Currently, there are no known official patches or countermeasures available for this vulnerability in BootDo due to its rolling release strategy and lack of specified affected versions.
Immediate mitigation steps include implementing CSRF protection mechanisms in the application, such as adding CSRF tokens to sensitive endpoints like /sys/user/save to verify legitimate user requests.
Additional recommended measures are:
- Implement prepared statements and parameter binding to prevent injection attacks.
- Enforce strict input validation and filtering to ensure all user inputs conform to expected formats.
- Minimize database user permissions by restricting the database account used by the application to the least privileges necessary, avoiding high-privilege accounts for routine operations.
If immediate patching is not possible, consider replacing the affected product or restricting access to the vulnerable endpoint through network controls or web application firewalls to reduce exposure.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The CVE-2026-1835 vulnerability allows attackers to perform unauthorized actions on behalf of authenticated users, including accessing sensitive user data and modifying account settings without consent.
Such unauthorized access and manipulation can lead to breaches of user privacy and compromise data integrity, which are critical concerns under regulations like GDPR and HIPAA.
Therefore, exploitation of this vulnerability could result in non-compliance with these standards due to failure to protect personal and sensitive information adequately.