Database disclosure via injectable payment identifier
Published Aug 26, 2022 · Updated Aug 3, 2024
SQL injection in Simple Task Scheduling System 1.0 allows remote attackers to read database data through a crafted delete-payment request. The delete_payment handler incorporates the POST id value into a database query without neutralizing quote-delimited SQL syntax, enabling error-based extraction through MySQL UpdateXML. Exploitation requires network access to the web endpoint; the published request demonstrates database-name disclosure without user interaction.
Summary
What happened
SQL injection in Simple Task Scheduling System 1.0 allows remote attackers to read database data through a crafted delete-payment request. The delete_payment handler incorporates the POST id value into a database query without neutralizing quote-delimited SQL syntax, enabling error-based extraction through MySQL UpdateXML. Exploitation requires network access to the web endpoint; the published request demonstrates database-name disclosure without user interaction.
The record
- CVE
- CVE-2022-36683
- Published
- Aug 26, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 26, 2022CVE 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?
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.
Weakness, pattern, technique
Public exploit references
- SQLi-6 delete_payment 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