CVE-2025-12293VulnerabilityPublished 27 Oct 2025

CVE-2025-12293: SourceCodester Point of Sales · SQL Injection

Affects SourceCodester Point of SalesSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 07:57 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 36% 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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Oct 2025
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 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
SourceCodester Point of Sales	Affected =1.0	Fixed in–

AI-suggested

1. Immediately monitor and restrict access to the /category.php endpoint, applying strict input validation and sanitization on the 'Category' parameter to prevent injection. 2. Deploy a web application firewall (WAF) with updated signatures to detect and block SQL injection attempts targeting this vulnerability. 3. Conduct thorough code reviews and security testing on the SourceCodester POS application to identify and remediate similar injection flaws. 4. Isolate POS systems from broader corporate networks to limit lateral movement in case of compromise. 5. Implement database least privilege principles, ensuring the POS application uses accounts with minimal permissions. 6. Regularly back up POS databases and verify integrity to enable recovery from potential data corruption. 7. Engage with the vendor or community to obtain and apply patches or updates as soon as they become available. 8. Educate staff on recognizing signs of POS compromise and establish incident response procedures tailored to retail environments.

Description

A vulnerability was identified in SourceCodester Point of Sales 1.0. This issue affects some unknown processing of the file /category.php. Such manipulation of the argument Category leads to sql injection. It is possible to launch the attack remotely. The exploit is publicly available and might be used.

Impact

For European organizations, exploitation of this SQL injection vulnerability could result in unauthorized access to sensitive customer and transaction data, leading to privacy violations and potential regulatory penalties under GDPR. Integrity of sales and inventory data could be compromised, causing financial discrepancies and loss of trust. Availability impacts might disrupt retail operations, affecting revenue and customer satisfaction. Retailers and service providers using SourceCodester POS in Europe, especially those with limited cybersecurity maturity, are at risk of targeted attacks. The presence of a public exploit increases the threat landscape, potentially attracting opportunistic attackers and cybercriminal groups. The medium severity score suggests moderate but tangible risks that could escalate if combined with other vulnerabilities or poor security practices. This threat underscores the importance of securing POS systems, which are frequent targets in the retail sector.

Summary

CVE-2025-12293 identifies a SQL injection vulnerability in SourceCodester Point of Sales version 1.0, specifically within the /category.php endpoint. The vulnerability arises from insufficient sanitization of the 'Category' parameter, which is directly used in SQL queries. This allows remote attackers to craft malicious input that alters the intended SQL command, potentially extracting sensitive data, modifying database contents, or disrupting service availability. The vulnerability requires no authentication or user interaction, making it highly accessible to attackers. The CVSS 4.0 base score is 6.9 (medium), reflecting the network attack vector, low complexity, and no privileges required. The impact on confidentiality, integrity, and availability is limited but non-negligible. Although no active exploitation has been reported, a public exploit exists, increasing the likelihood of future attacks. The lack of vendor patches at the time of disclosure necessitates immediate defensive actions. This vulnerability is particularly critical for organizations relying on SourceCodester POS for transaction processing, as compromise could lead to financial fraud, leakage of customer data, and operational interruptions.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Nov 2025, 16:56 UTC

Technical details

References

Community reviews

Related threats