Skip to main content
CVE-2024-33303VulnerabilityPublished Updated

CVE-2024-33303: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 8.2 High.

Data as of 25 Oct 2026, 19:02 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 May 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

1. Implement strict input validation and output encoding on the 'First Name' field and all user-supplied inputs to neutralize malicious scripts. Use context-aware encoding (e.g., HTML entity encoding) to prevent script execution. 2. Deploy a Web Application Firewall (WAF) with rules to detect and block common XSS attack patterns targeting the affected endpoints. 3. Educate users and administrators about the risks of clicking untrusted links or submitting untrusted input. 4. Monitor logs for suspicious activity related to the Add Users functionality to detect potential exploitation attempts. 5. If possible, restrict access to the Add Users feature to trusted users and enforce multi-factor authentication to reduce risk. 6. Follow vendor updates closely and apply patches immediately once available. 7. Conduct regular security assessments and penetration testing focusing on input validation weaknesses. 8. Consider implementing Content Security Policy (CSP) headers to limit the impact of injected scripts if exploitation occurs.

Description

SourceCodester Product Show Room 1.0 is vulnerable to Cross Site Scripting (XSS) via "First Name" under Add Users.

References

Community reviews

Loading reviews…