Database compromise via editorder.php id injection
Published Nov 23, 2022 · Updated Apr 28, 2025
SQL injection in Billing System Project 1.0 allows remote attackers to manipulate database queries through the id parameter in editorder.php. The public record identifies the injection point but does not disclose the exact SQL statement or missing neutralization operation. No authentication or user interaction is required; exploitation grants database read and write access and can interrupt the service.
Summary
What happened
SQL injection in Billing System Project 1.0 allows remote attackers to manipulate database queries through the id parameter in editorder.php. The public record identifies the injection point but does not disclose the exact SQL statement or missing neutralization operation. No authentication or user interaction is required; exploitation grants database read and write access and can interrupt the service.
The record
- CVE
- CVE-2022-43213
- Published
- Nov 23, 2022
- Updated
- Apr 28, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 23, 2022CVE publishedPublication date reported by the CVE source.
- Apr 28, 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.
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
- CVE-2022-43213 editorder.php SQL injection proof of conceptproof of concept · unverified
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