Username enumeration via unescaped search wildcards
Published Apr 21, 2025 · Updated May 12, 2025
Improper access control in FlaskBlog 2.6.1 allows remote attackers to enumerate all usernames through the public search route. The search function wraps untrusted query text in SQL LIKE wildcards without escaping attacker-supplied % or _, so either character matches every stored username. No authentication or user interaction is required, and the demonstrated consequence is disclosure of account names.
Summary
What happened
Improper access control in FlaskBlog 2.6.1 allows remote attackers to enumerate all usernames through the public search route. The search function wraps untrusted query text in SQL LIKE wildcards without escaping attacker-supplied % or _, so either character matches every stored username. No authentication or user interaction is required, and the demonstrated consequence is disclosure of account names.
The record
- CVE
- CVE-2025-28104
- Published
- Apr 21, 2025
- Updated
- May 12, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-284, T1087
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 21, 2025CVE publishedPublication date reported by the CVE source.
- May 12, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Public exploit references
- Wildcard username-enumeration proof of conceptproof of concept · demonstrated
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