Unauthenticated SQL Injection in the WordPress plugin Aeroscroll Gallery (1.0.13)
Aeroscroll Gallery (WordPress.org, version 1.0.13) Aeroscroll Gallery (1.0.13) exposes an unauthenticated WordPress REST route (aeroscroll/v1) whose handler builds a SQL query by string concatenation. A numeric guard is applied to one request parameter, but a second, unguarded parameter is concatenated into the query, so an unauthenticated request can inject SQL and read arbitrary database contents (WordPress user password hashes, secrets). No fixed release is available.
Aeroscroll Gallery 1.0.13 (WordPress.org) contains an unauthenticated sql injection. The plugin registers a handler reachable by visitors who are not logged in, and it concatenates a request parameter straight into a live SQL statement.
The unauthenticated endpoint validates one request parameter with a numeric check, but the SQL query concatenates a different request parameter that is never validated anywhere, so that value reaches the database completely unsanitised. The result is a blind/time-based SQL-injection channel through which the full database (user password hashes, secrets) can be extracted.
Aeroscroll Gallery was surfaced automatically by the codelake WordPress static-analysis pipeline (source-to-sink taint) · AI false-positive triage · manual source verification, and then verified by hand against the shipped 1.0.13 artifact.
Class: SQL Injection (CWE-89). Privilege required: none — the injectable endpoint is registered for logged-out visitors. Effect: read access to the entire database via blind SQL injection (credential hashes, secrets, tokens); depending on database privileges, write access.
The precise sink locations and code are withheld below until the disclosure deadline.
0:00 UTC
Detected by codelake Research · codelake WordPress static-analysis pipeline (source-to-sink taint) · AI false-positive triage · manual source verification · disclosed to WordPress Plugin Security Team before publication.
This is a coordinated vulnerability disclosure. The affected package, version and class are published immediately so defenders can act; the exact code location and reproduction are withheld until the deadline, and no weaponised proof-of-concept is published. The archived artifact is available to verified security researchers on request.