Skip to main content
CVE-2025-13280VulnerabilityPublished Updated

CVE-2025-13280: CodeAstro Simple Inventory System · SQL Injection

Affects CodeAstro Simple Inventory SystemSource CVE Database V5

0

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Nov 2025

  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

Affected software

ProductAffectedFixed in
CodeAstro Simple Inventory SystemAffected
  • =1.0
Fixed in–

AI-suggested

To mitigate CVE-2025-13280, organizations should immediately implement the following measures: 1) Apply any available patches or updates from CodeAstro as soon as they are released. 2) If patches are not yet available, implement input validation and sanitization on the Username parameter to reject or properly escape malicious SQL syntax. 3) Refactor the code to use parameterized queries or prepared statements rather than dynamic SQL concatenation to prevent injection. 4) Restrict database user permissions to the minimum necessary, limiting the impact of a successful injection. 5) Deploy Web Application Firewalls (WAFs) with rules targeting SQL Injection patterns to detect and block exploit attempts. 6) Monitor logs for suspicious login attempts or unusual database queries indicative of exploitation. 7) Conduct security code reviews and penetration testing focused on injection vulnerabilities in authentication modules. 8) Educate developers on secure coding practices to prevent similar issues in future releases. These targeted actions go beyond generic advice by focusing on the specific vulnerable component and practical interim controls until official fixes are available.

Description

A vulnerability was determined in CodeAstro Simple Inventory System 1.0. The impacted element is an unknown function of the file /index.php of the component Login. Executing a manipulation of the argument Username can lead to sql injection. The attack may be launched remotely. The exploit has been publicly disclosed and may be utilized.

References

Community reviews

Loading reviews…