Skip to main content
CVE-2024-33275VulnerabilityPublished Updated

CVE-2024-33275: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 25 Oct 2026, 19:02 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 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 2026-10-25.

What to do

AI-suggested

To mitigate CVE-2024-33275, organizations should immediately implement the following measures: 1) Apply any official patches or updates from Webbax as soon as they become available. 2) If patches are not yet released, implement Web Application Firewall (WAF) rules to detect and block SQL injection attempts targeting product_search.php. 3) Conduct thorough input validation and sanitize all user-supplied data in the Super Newsletter module, especially in product search parameters. 4) Employ parameterized queries or prepared statements in the backend code to prevent SQL injection. 5) Restrict database user privileges to the minimum necessary to limit the impact of potential exploitation. 6) Monitor logs for unusual database queries or access patterns indicative of exploitation attempts. 7) Educate development and security teams about secure coding practices to prevent similar vulnerabilities. 8) Consider isolating or disabling the vulnerable module temporarily if immediate patching is not feasible.

Description

SQL injection vulnerability in Webbax supernewsletter v.1.4.21 and before allows a remote attacker to escalate privileges via the Super Newsletter module in the product_search.php components.

References

Community reviews

Loading reviews…