Skip to main content
VulnerabilityPublished Updated

CVE-2024-30974: autoexpress · SQL Injection

Affects autoexpressSource CVE Database V5

0

Not known to be exploited · CVSS 7.3 High.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
7.3High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Apr 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubtorchstar/autoexpresspkg:github/torchstar/autoexpressOther threatsAffected
  • =1.3.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate this vulnerability, organizations should immediately audit and sanitize all inputs to the carId parameter, implementing strict input validation and parameterized queries or prepared statements to prevent SQL injection. Restrict local access to the affected application to trusted users only and monitor for unusual database queries or access patterns. Employ database activity monitoring and intrusion detection systems to detect potential exploitation attempts. If possible, isolate the vulnerable application in a segmented network environment to limit lateral movement. Since no official patches are available, consider applying virtual patching via web application firewalls (WAFs) configured to block malicious SQL payloads targeting the carId parameter. Additionally, conduct thorough code reviews and security testing on the autoexpress application and plan for prompt patch deployment once available from the vendor.

Description

SQL Injection vulnerability in autoexpress v.1.3.0 allows attackers to run arbitrary SQL commands via the carId parameter.

References

Community reviews

Loading reviews…