Brute-force login via unattached throttle
Published Aug 18, 2026 · Updated Aug 18, 2026
Missing rate limiting in Plainpad 1.1.1 and earlier allows remote attackers to brute-force accounts and interrupt service via POST /v1/sessions. The login route accepts unauthenticated requests without any effective throttle because App\Http\Kernel.php defines the api limiter in dead code under the Laravel 11+ skeleton, bootstrap/app.php never calls throttleApi(), and the route lacks a dedicated throttle middleware. Any internet-reachable Plainpad instance exposes the login API; attackers with a known email address can run unlimited password guesses and drive repeated bcrypt checks until CPU use rises, but the record does not indicate direct code execution or data modification.
Summary
What happened
Missing rate limiting in Plainpad 1.1.1 and earlier allows remote attackers to brute-force accounts and interrupt service via POST /v1/sessions. The login route accepts unauthenticated requests without any effective throttle because App\Http\Kernel.php defines the api limiter in dead code under the Laravel 11+ skeleton, bootstrap/app.php never calls throttleApi(), and the route lacks a dedicated throttle middleware. Any internet-reachable Plainpad instance exposes the login API; attackers with a known email address can run unlimited password guesses and drive repeated bcrypt checks until CPU use rises, but the record does not indicate direct code execution or data modification.
The record
- CVE
- CVE-2026-73529
- Published
- Aug 18, 2026
- Updated
- Aug 18, 2026
- Vendor
- Alex Tselegidis
- Product
- Plainpad
- Classifications
- CWE-307, T1110
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 18, 2026CVE publishedPublication date reported by the CVE source.
- Aug 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.1.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo