Security readout for executives and security teams
Plain-English summary
Courier Management System 1.0 has a reported SQL injection flaw in an administrative PHP endpoint. If this software is deployed, database-backed courier records may be at risk. The public sources do not provide a vendor advisory, CVSS score, patch status, or evidence of active exploitation.
Executive priority
Prioritize quickly if this application is deployed in production or exposed to the internet. The main uncertainty is not exploitability, but whether the software exists in your environment and whether a trusted fix is available.
Technical view
CVE-2020-35327 describes SQL injection through the ref_no POST parameter in admin_class.php for Courier Management System 1.0. The record cites an Exploit-DB entry, indicating public exploit information exists. Sources do not confirm authentication requirements, reachable routes, database impact, or remediation details.
Likely exposure
Exposure is likely limited to organizations running Courier Management System 1.0, especially if the admin_class.php endpoint is internet-accessible. Asset discovery is required because the CVE record lists affected vendor and product metadata as n/a.
Exploitation context
Public exploit information is referenced by Exploit-DB, but CISA KEV is false in the provided bundle. There is no cited evidence of active exploitation, mass scanning, or ransomware use.
Researcher notes
The source record is sparse: no CVSS, CWE, CPE, vendor, patch, or authentication context. Treat Exploit-DB as evidence of public exploit knowledge, not proof of active exploitation. Avoid assuming impact beyond SQL injection without local validation.
Mitigation direction
- Identify any Courier Management System 1.0 deployments.
- Restrict external access to administrative PHP endpoints.
- Check vendor or project guidance for patches or maintained replacements.
- Review application code for safe parameterized database queries.
- Prioritize retirement if no supported fix exists.
Validation and detection
- Search web roots and inventories for Courier Management System 1.0.
- Confirm whether admin_class.php is deployed and reachable.
- Review logs for suspicious POST requests involving ref_no.
- Verify database access uses parameterized queries for ref_no handling.
- Document whether authentication protects the affected endpoint.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
Database behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2020-35327 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://www.exploit-db.com/exploits/49243CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.