Skip to main content
VulnerabilityPublished

CVE-2026-30564: SourceCodester Sales · Cross-site Scripting

Source CVE Database V5

0

Not known to be exploited · CVSS 6.1 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 10% 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:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Mar 2026

  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

AI-suggested

To mitigate this vulnerability, organizations should immediately implement input validation and output encoding for the 'limit' parameter in the view_payments.php file to ensure that any user-supplied data is properly sanitized before being reflected in the web page. Employing a Content Security Policy (CSP) can help restrict the execution of unauthorized scripts. Deploying a Web Application Firewall (WAF) with rules to detect and block reflected XSS attacks can provide an additional layer of defense. Educate users to avoid clicking suspicious links and implement monitoring to detect anomalous activities related to this vulnerability. Regularly review and update the software to newer, secure versions when released by the vendor or community.

Description

A Reflected Cross-Site Scripting (XSS) vulnerability exists in SourceCodester Sales and Inventory System 1.0. The vulnerability is located in the view_payments.php file via the "limit" parameter. The application fails to sanitize the input, allowing remote attackers to inject arbitrary web script or HTML via a crafted URL.

References

Community reviews

Loading reviews…