Database disclosure via injectable Staff record identifier
Published Aug 18, 2021 · Updated Aug 4, 2024
SQL injection in LJCMS 1.3 allows remote authenticated users to read sensitive database data through a crafted Staff request. The Staff read action at /oa.php?c=Staff&a=read interprets the POST id value as SQL syntax, so a closing parenthesis and UNION SELECT return attacker-chosen database values. The published path requires an OA session, but documented default administrator credentials expose unchanged installations; successful exploitation discloses database contents without modifying them.
Summary
What happened
SQL injection in LJCMS 1.3 allows remote authenticated users to read sensitive database data through a crafted Staff request. The Staff read action at /oa.php?c=Staff&a=read interprets the POST id value as SQL syntax, so a closing parenthesis and UNION SELECT return attacker-chosen database values. The published path requires an OA session, but documented default administrator credentials expose unchanged installations; successful exploitation discloses database contents without modifying them.
The record
- CVE
- CVE-2020-22122
- Published
- Aug 18, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 18, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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.
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
- Find a Place LJCMS 1.3 Staff read 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