CVE-2025-12306VulnerabilityPublished 27 Oct 2025

CVE-2025-12306: code-projects Nero Social Networking Site · SQL Injection

Affects code-projects Nero Social Networking SiteSource 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 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-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 Nero Social Networking Site	Affected =1.0	Fixed in–

AI-suggested

1. Conduct an immediate code audit of the /acceptoffres.php file to identify and remediate the SQL injection vulnerability by implementing parameterized queries or prepared statements. 2. Apply strict input validation and sanitization on all user-supplied parameters, especially the 'ID' parameter, to prevent malicious SQL code injection. 3. Deploy or update Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting the vulnerable endpoint. 4. Monitor application logs and network traffic for unusual or suspicious activity related to the /acceptoffres.php endpoint. 5. If possible, isolate or restrict access to the vulnerable application until a patch or fix is applied. 6. Engage with the vendor or development community to obtain or develop an official patch or update for Nero Social Networking Site 1.0. 7. Educate development and security teams about secure coding practices to prevent similar vulnerabilities in future releases. 8. Perform regular vulnerability scanning and penetration testing focused on SQL injection vectors to ensure ongoing protection.

Description

A vulnerability was determined in code-projects Nero Social Networking Site 1.0. Affected is an unknown function of the file /acceptoffres.php. This manipulation of the argument ID causes sql injection. The attack is possible to be carried out remotely. The exploit has been publicly disclosed and may be utilized.

Impact

For European organizations using Nero Social Networking Site 1.0, this vulnerability poses risks including unauthorized access to sensitive user data, data tampering, and potential service outages. The SQL injection could allow attackers to extract personally identifiable information (PII), manipulate user accounts, or corrupt database contents, leading to loss of data integrity and availability. Given the GDPR regulations in Europe, any data breach involving personal data could result in substantial fines and legal repercussions. Social networking platforms often hold large volumes of user-generated content and personal information, making them attractive targets for attackers. The remote and unauthenticated nature of the exploit increases the threat level, as attackers can attempt exploitation without prior access. The medium severity rating suggests that while the impact is significant, it may not lead to complete system compromise or widespread disruption without additional factors. However, the public disclosure increases the urgency for European organizations to address this vulnerability promptly to avoid reputational damage and regulatory penalties.

Summary

CVE-2025-12306 identifies a SQL injection vulnerability in the Nero Social Networking Site version 1.0, specifically within the /acceptoffres.php file. The vulnerability arises from improper input validation of the 'ID' parameter, which can be manipulated by remote attackers to inject malicious SQL queries. This flaw allows attackers to execute arbitrary SQL commands on the backend database without requiring authentication or user interaction, making exploitation straightforward. The vulnerability was publicly disclosed shortly after its discovery, increasing the likelihood of exploitation attempts. The CVSS 4.0 vector indicates a network attack vector (AV:N), no privileges required (PR:N), no user interaction (UI:N), and partial impacts on confidentiality, integrity, and availability (VC:L, VI:L, VA:L). While no exploits are currently known in the wild, the public disclosure necessitates urgent attention. The vulnerability could lead to unauthorized data access, data modification, or denial of service conditions, depending on the attacker's objectives and database permissions. The absence of patches or vendor-provided fixes means organizations must implement interim mitigations such as input validation and web application firewall rules. Given the nature of social networking sites, the potential exposure of user data and disruption of services could have significant reputational and regulatory consequences.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Oct 2025, 19:07 UTC

Technical details

References

Community reviews

Related threats