CVE-2025-12928VulnerabilityPublished 10 Nov 2025

CVE-2025-12928: code-projects Online Job Search Engine · SQL Injection

Affects code-projects Online Job Search EngineSource CVE Database V5

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 40% 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 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
code-projects Online Job Search Engine	Affected =1.0	Fixed in–

AI-suggested

Organizations should immediately implement input validation and sanitization on all user-supplied data, especially the username and phone parameters in the /login.php script. Employing parameterized queries or prepared statements is critical to prevent SQL injection. If possible, upgrade to a patched version of the software once available or apply vendor-provided fixes. In the absence of official patches, consider deploying web application firewalls (WAFs) with rules to detect and block SQL injection attempts targeting the login endpoint. Conduct thorough code reviews and security testing to identify and remediate similar injection flaws elsewhere in the application. Monitor logs for suspicious login attempts or anomalous database queries indicative of exploitation attempts. Additionally, restrict database user permissions to the minimum necessary to limit the impact of any successful injection. Educate development teams on secure coding practices to prevent recurrence. Finally, ensure regular backups of databases to enable recovery in case of data corruption or loss.

Description

A vulnerability was detected in code-projects Online Job Search Engine 1.0. This affects an unknown function of the file /login.php. Performing manipulation of the argument username/phone results in sql injection. The attack is possible to be carried out remotely. The exploit is now public and may be used.

Impact

For European organizations using the affected Online Job Search Engine, this vulnerability poses a significant risk to the confidentiality and integrity of user data, including personal and login information. Exploitation could lead to unauthorized access to sensitive data, data leakage, or unauthorized modifications, undermining trust and potentially violating GDPR requirements. Service availability could also be impacted if attackers manipulate the database to disrupt operations. The public availability of exploit code increases the likelihood of attacks, especially targeting organizations that have not applied mitigations. Given the widespread use of online job platforms in Europe and the sensitivity of employment-related data, this vulnerability could have reputational and regulatory consequences. Organizations in sectors such as recruitment, human resources, and employment services are particularly at risk. The vulnerability's remote exploitability without authentication means attackers can operate from anywhere, increasing the threat landscape for European entities.

Summary

CVE-2025-12928 is an SQL Injection vulnerability affecting the code-projects Online Job Search Engine version 1.0. The vulnerability resides in the /login.php script, where the username or phone parameters are improperly sanitized, allowing attackers to inject malicious SQL code. This injection flaw enables remote attackers to execute arbitrary SQL queries on the backend database without requiring authentication or user interaction. The vulnerability is exploitable over the network, making it accessible to any attacker who can reach the login endpoint. The CVSS 4.0 score of 6.9 reflects a medium severity, considering the attack vector is network-based with low complexity and no privileges or user interaction needed, but with limited impact on confidentiality, integrity, and availability. The exploit code has been publicly disclosed, increasing the risk of exploitation. The lack of official patches or updates means organizations must implement immediate mitigations. The vulnerability could allow attackers to bypass authentication, extract sensitive user data, or modify database contents, potentially leading to data breaches or service disruption. This is particularly concerning for organizations relying on this job search engine to manage user credentials and personal information. The vulnerability highlights the critical need for secure coding practices such as input validation and use of prepared statements to prevent SQL injection attacks.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats