Authenticated SQL injection via unsanitized deletion identifier
Published Nov 8, 2021 · Updated Aug 3, 2024
SQL injection in Unlimited PopUps 4.5.3 and earlier allows remote authenticated users to alter database queries through the did parameter. The popup deletion handler in popuplist.php concatenates the did GET value directly after the id predicate without sanitization, validation, escaping, or a prepared statement. An Editor account can reach the handler and use crafted SQL to read or modify the WordPress database or interrupt database service.
Summary
What happened
SQL injection in Unlimited PopUps 4.5.3 and earlier allows remote authenticated users to alter database queries through the did parameter. The popup deletion handler in popuplist.php concatenates the did GET value directly after the id predicate without sanitization, validation, escaping, or a prepared statement. An Editor account can reach the handler and use crafted SQL to read or modify the WordPress database or interrupt database service.
The record
- CVE
- CVE-2021-24631
- Published
- Nov 8, 2021
- Updated
- Aug 3, 2024
- Vendor
- Samina Naz
- Product
- Unlimited PopUps
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 8, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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=4.5.3 <=4.5.3
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
Public exploit references
- CodeVigilant time-based SQL injection proof of conceptfunctional · 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