An unauthenticated SQL injection vulnerability in Kepler Wallpaper Script 1.1 poses a significant risk of unauthorized database information disclosure.

The application fails to properly sanitize user input in the category parameter, which is processed by the database layer. An unauthenticated attacker can exploit this by sending crafted GET requests containing SQL UNION statements to extract database content, including usernames and version details.

Successful exploitation of this vulnerability allows unauthorized access to the underlying database, potentially leading to the compromise of sensitive administrative credentials or configuration data. Given the CVSS score of 8.2, this flaw is categorized as High severity, as it facilitates unauthorized data exfiltration without requiring any user interaction or prior authentication.

Immediate Action: There is no official security patch provided by the vendor; users should immediately discontinue use of the script or implement strict input validation on the category parameter.

Proactive Monitoring: Security teams should monitor web server access logs for anomalous GET requests containing SQL syntax, such as UNION, SELECT, or hexadecimal encoding, directed at the category endpoint.

Compensating Controls: Deploy a Web Application Firewall (WAF) with custom rulesets designed to detect and block SQL injection patterns specifically targeting the category parameter.

Public Exploit Available: Yes, a functional proof-of-concept exists as documented in the Exploit-DB entry 46207.

Due to the lack of an official vendor patch and the availability of a published exploit, this vulnerability presents a persistent risk to any deployment of Kepler Wallpaper Script 1.1. Organizations using this software should prioritize migrating to a supported and secure alternative, as the current implementation cannot be considered safe for public-facing environments.