CVE-2024-33273: shipup · SQL Injection
Affects shipupSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 3.3.0 as a priority.
Data as of 26 Oct 2026, 12:54 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.3.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 30 Apr 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
Upgrade shipup to 3.3.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
npmshipuppkg:npm/shipupOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until an official patch for Shipup 3.3.0 or later is applied, organizations should implement multiple layers of defense. First, deploy web application firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting the getShopID function. Conduct thorough input validation and sanitization on all user-supplied data, especially parameters interacting with database queries. Restrict database permissions to the minimum necessary to limit the impact of potential exploitation. Monitor database logs and application logs for unusual query patterns or repeated failed attempts indicative of injection attacks. Employ network segmentation to isolate critical systems and reduce lateral movement risk. Engage with Shipup support or vendor channels to obtain patches or official guidance promptly. Additionally, conduct security awareness training for developers to avoid similar injection flaws in future code. Prepare incident response plans to quickly contain and remediate any exploitation attempts.
Description
SQL injection vulnerability in shipup before v.3.3.0 allows a remote attacker to escalate privileges via the getShopID function.