CVE-2025-11583VulnerabilityPublished 10 Oct 2025

CVE-2025-11583: 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, 08:30 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 26 Oct 2026.

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

European organizations should immediately audit their use of the code-projects Online Job Search Engine to identify any deployments of version 1.0. Employing Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting /postjob.php can provide interim protection. Regularly monitoring logs for suspicious query patterns or repeated access attempts to the vulnerable endpoint is critical. Organizations should also consider isolating the affected application from sensitive backend systems and databases to limit potential damage. Conducting penetration testing focused on injection flaws can help verify the effectiveness of mitigations. Finally, organizations should engage with the vendor or community for updates and patches and plan for an upgrade or replacement of the vulnerable software version.

Description

A flaw has been found in code-projects Online Job Search Engine 1.0. Impacted is an unknown function of the file /postjob.php. Executing manipulation of the argument txtjobID can lead to sql injection. The attack may be launched remotely. The exploit has been published and may be used.

Impact

For European organizations using the code-projects Online Job Search Engine 1.0, this vulnerability could lead to unauthorized disclosure of sensitive job posting data, candidate information, or internal business data stored in the backend database. Attackers could manipulate or delete data, undermining the integrity and availability of the job search platform. This could result in reputational damage, regulatory non-compliance (especially under GDPR if personal data is exposed), and operational disruptions. The remote and unauthenticated nature of the exploit increases the risk of widespread attacks, particularly targeting recruitment agencies, HR departments, and job boards that rely on this software. The medium severity rating suggests moderate but actionable risk, with potential for escalation if combined with other vulnerabilities or misconfigurations. The lack of known active exploits provides a window for proactive defense but also means organizations should not delay remediation. The impact on availability could disrupt recruitment processes, affecting business continuity and talent acquisition efforts.

Summary

CVE-2025-11583 identifies a SQL injection vulnerability in the code-projects Online Job Search Engine version 1.0, specifically within the /postjob.php script. The vulnerability arises from improper handling of the txtjobID parameter, which is susceptible to direct manipulation by remote attackers without any authentication or user interaction. This allows attackers to inject malicious SQL code into backend database queries, potentially enabling unauthorized access to sensitive data, data modification, or even deletion. The vulnerability is exploitable over the network (AV:N) with low attack complexity (AC:L), no privileges required (PR:N), and no user interaction needed (UI:N). The impact on confidentiality, integrity, and availability is low individually but combined can lead to significant data exposure or service disruption. The exploit has been publicly disclosed, increasing the risk of exploitation despite no known active attacks. The lack of patches or vendor-provided fixes necessitates immediate mitigation by users. The vulnerability affects only version 1.0 of the product, which may limit exposure but still poses a risk to organizations relying on this software for job posting and search functionalities. The CVSS vector indicates partial impact on confidentiality, integrity, and availability, emphasizing the need for input validation and secure coding practices to prevent exploitation.

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