CVE-2026-30351

7.5

leonvanzyl · autocoder

A path traversal vulnerability in the UI/static component of leonvanzyl autocoder allows unauthenticated attackers to read arbitrary files via crafted URL sequences.

Executive summary

A path traversal vulnerability in the leonvanzyl autocoder component enables unauthenticated attackers to read arbitrary files from the host system, posing a significant risk to data confidentiality.

Vulnerability

This is a path traversal vulnerability (CWE-22) residing in the UI/static component of the software. The vulnerability allows an unauthenticated remote attacker to bypass directory restrictions and access sensitive files by submitting specifically crafted URL paths.

Business impact

The ability to read arbitrary files can lead to the exposure of sensitive configuration data, environment variables, or system credentials. This breach of confidentiality could facilitate further attacks or compromise proprietary intellectual property. With a CVSS score of 7.5, this high severity vulnerability necessitates immediate attention to prevent unauthorized information disclosure.

Remediation

Immediate Action: Review the official leonvanzyl autocoder repository for updates or security patches. If no official patch is available, implement strict input validation to sanitize all URL path inputs and block directory traversal sequences.

Proactive Monitoring: Monitor web server access logs for anomalous requests containing dot-dot-slash (../) sequences or suspicious file extension access patterns.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to detect and block directory traversal attempts directed at the application.

Exploitation status

Public Exploit Available: Yes, a published proof-of-concept exists (referenced in the GitHub gist provided by the security researcher).

Analyst recommendation

Given the accessibility of this vulnerability to unauthenticated attackers and the availability of a public proof-of-concept, users should prioritize securing their installations. Administrators must verify their version status against the vendor repository and apply available mitigations immediately to prevent potential data exposure. If a direct patch is not yet released, isolating the application from public internet access is the most effective temporary measure.

Sources