CVE-2025-11582VulnerabilityPublished 10 Oct 2025

CVE-2025-11582: 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 26 Oct 2026, 06:26 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 10 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
code-projects Online Job Search Engine	Affected =1.0	Fixed in–

AI-suggested

Since no official patches are currently available, European organizations should implement immediate compensating controls. These include applying strict input validation and sanitization on the txtusername parameter, ideally using parameterized queries or prepared statements to prevent SQL injection. Web application firewalls (WAFs) should be configured to detect and block SQL injection payloads targeting /registration.php. Conduct thorough code reviews and penetration testing focused on input handling in the registration module. Monitor logs for unusual database query patterns or repeated failed registration attempts indicative of exploitation attempts. Limit database user privileges to the minimum necessary to reduce potential damage. If possible, isolate the vulnerable application from critical internal networks. Organizations should also engage with the vendor for updates and consider migrating to alternative platforms if remediation is delayed. Regular backups and incident response plans should be updated to address potential exploitation scenarios.

Description

A vulnerability was detected in code-projects Online Job Search Engine 1.0. This issue affects some unknown processing of the file /registration.php. Performing manipulation of the argument txtusername results in sql injection. The attack may be initiated remotely. The exploit is now public and may be used.

Impact

For European organizations using the code-projects Online Job Search Engine 1.0, this vulnerability poses a risk of unauthorized access to sensitive user data such as personal information submitted during registration. Attackers could manipulate database queries to extract confidential data, alter user records, or disrupt service availability. This could lead to data breaches, reputational damage, and regulatory non-compliance under GDPR. The impact is particularly significant for recruitment agencies, job boards, and HR departments relying on this platform for candidate management. The medium severity rating reflects partial impact on confidentiality, integrity, and availability, but the ease of exploitation and remote attack vector increase the threat level. Organizations may face targeted attacks aiming to harvest personal data or sabotage recruitment operations. Additionally, compromised systems could be used as pivot points for further network intrusion.

Summary

CVE-2025-11582 is a SQL injection vulnerability identified in version 1.0 of the code-projects Online Job Search Engine, specifically in the /registration.php endpoint. The vulnerability arises from improper sanitization or validation of the txtusername parameter, which is susceptible to SQL injection attacks. An attacker can remotely send crafted input to this parameter to manipulate backend SQL queries, potentially extracting sensitive information, modifying database contents, or bypassing authentication mechanisms. The vulnerability requires no authentication or user interaction and can be exploited over the network, increasing its risk profile. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P) indicates network attack vector, low attack complexity, no privileges or user interaction required, and partial impact on confidentiality, integrity, and availability. Although no known exploits are currently active in the wild, the public availability of exploit code increases the likelihood of exploitation attempts. The lack of available patches or vendor advisories necessitates immediate attention from users of this software. The vulnerability could allow attackers to access or alter user registration data, potentially compromising user privacy and the integrity of the recruitment platform.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Oct 2025, 20:22 UTC

Technical details

References

Community reviews

Related threats