Unauthenticated command execution via unfiltered DB Name
Published Sep 2, 2021 · Updated Aug 4, 2024
Command injection in CraigMS 1.0 allows remote attackers to execute arbitrary commands through crafted input in the DB Name field. craigms/main.php accepts the posted DB Name value at line 74 without filtering and uses it in the command-execution path. The page is network-reachable without authentication, and exploitation requires the supplied database name to exist in MySQL.
Summary
What happened
Command injection in CraigMS 1.0 allows remote attackers to execute arbitrary commands through crafted input in the DB Name field. craigms/main.php accepts the posted DB Name value at line 74 without filtering and uses it in the command-execution path. The page is network-reachable without authentication, and exploitation requires the supplied database name to exist in MySQL.
The record
- CVE
- CVE-2020-18048
- Published
- Sep 2, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-77, T1059
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 2, 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
- CraigMS main.php command-execution 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