CVE-2025-12926VulnerabilityPublished 10 Nov 2025

CVE-2025-12926: SourceCodester Farm Management System · SQL Injection

Affects SourceCodester Farm Management SystemSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/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: Low
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: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
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 10 Nov 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-25.

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 Farm Management System	Affected =1.0	Fixed in–

AI-suggested

1. Immediately implement input validation and sanitization on the 'pid' parameter in /review.php to prevent SQL injection. 2. Refactor the code to use parameterized queries or prepared statements to eliminate direct SQL concatenation. 3. Restrict database user permissions to the minimum necessary to limit the impact of potential exploitation. 4. Monitor logs for suspicious SQL query patterns or unusual database activity related to /review.php. 5. Isolate the farm management system network segment to reduce exposure to external threats. 6. Engage with SourceCodester or community forums to obtain or develop patches or updated versions. 7. Conduct regular security assessments and penetration testing focused on input validation and injection flaws. 8. Educate staff on the risks of SQL injection and ensure secure coding practices are followed for any customizations.

Description

A weakness has been identified in SourceCodester Farm Management System 1.0. The affected element is an unknown function of the file /review.php. This manipulation of the argument pid causes sql injection. Remote exploitation of the attack is possible. The exploit has been made available to the public and could be exploited.

Impact

For European organizations, especially those in the agricultural sector relying on SourceCodester Farm Management System 1.0, this vulnerability could lead to unauthorized access to sensitive farm data, including production metrics, financial records, and resource inventories. Attackers could alter or delete critical data, impacting decision-making and operational continuity. Data breaches could also lead to regulatory non-compliance under GDPR, resulting in legal and financial penalties. Disruption of farm management systems could affect supply chains and food production, with broader economic implications. Although the impact is rated medium, the critical nature of agricultural data and potential cascading effects on food security elevate the importance of addressing this vulnerability promptly.

Summary

CVE-2025-12926 identifies a SQL injection vulnerability in SourceCodester Farm Management System version 1.0, specifically in the /review.php script where the 'pid' parameter is improperly sanitized. This allows an attacker to inject malicious SQL code remotely without requiring authentication or user interaction, exploiting the system's database backend. The vulnerability arises from insufficient input validation and lack of prepared statements, enabling attackers to manipulate database queries, potentially extracting sensitive data, modifying records, or causing denial of service. The CVSS 4.0 vector indicates network attack vector, low attack complexity, no privileges or user interaction needed, and limited impact on confidentiality, integrity, and availability. Although the exploit is publicly available, no active exploitation has been confirmed. The vulnerability affects only version 1.0 of the product, which is used for farm management tasks such as crop, livestock, and resource tracking. The absence of official patches necessitates immediate mitigation efforts by users. This vulnerability is significant because farm management systems often contain sensitive operational and business data, and compromise could disrupt agricultural operations or expose proprietary information.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Nov 2025, 04:47 UTC

Technical details

References

Community reviews

Related threats