VulnerabilityPublished 25 Feb 2026Updated 26 Feb 2026

CVE-2026-3135: itsourcecode News Portal Project · SQL Injection

Affects itsourcecode News Portal ProjectSource CVE Database V5

Compare

Public exploit available · CVSS 6.9 Medium.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 4.0 base score

6.9Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 31% 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 25 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 29 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity 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
itsourcecodeNews Portal Project	Affected =1.0	Fixed in–

AI-suggested

To mitigate CVE-2026-3135, organizations should immediately implement the following specific measures: 1) Apply input validation and sanitization on the 'Category' parameter in /admin/add-category.php to ensure only expected values are accepted; 2) Refactor database queries to use parameterized prepared statements or stored procedures to prevent SQL injection; 3) Restrict access to the /admin directory using network-level controls such as IP whitelisting or VPN access to limit exposure; 4) Employ web application firewalls (WAFs) configured to detect and block SQL injection patterns targeting this endpoint; 5) Conduct thorough code reviews and security testing on all input handling components of the News Portal Project; 6) Monitor logs for suspicious database query patterns or unusual admin activity; 7) If possible, upgrade to a patched or newer version of the software once available; 8) Educate developers and administrators on secure coding and deployment practices to prevent similar vulnerabilities. These targeted actions go beyond generic advice by focusing on the specific vulnerable parameter and administrative context.

Description

A weakness has been identified in itsourcecode News Portal Project 1.0. The impacted element is an unknown function of the file /admin/add-category.php. This manipulation of the argument Category causes sql injection. It is possible to initiate the attack remotely. The exploit has been made available to the public and could be used for attacks.

Impact

The SQL Injection vulnerability in the News Portal Project can have significant impacts on affected organizations. Attackers exploiting this flaw can remotely execute arbitrary SQL commands, potentially leading to unauthorized access to sensitive data such as user credentials, news content, or administrative information. Data integrity may be compromised by unauthorized modifications or deletions of database records, disrupting the reliability of the news portal. Availability could also be affected if attackers execute destructive queries or cause database errors, leading to service outages. Given the administrative context of the vulnerable script, attackers might escalate their control over the application or pivot to other internal systems. Organizations relying on this software for public-facing news dissemination could suffer reputational damage, legal liabilities, and operational disruptions. The availability of a public exploit increases the risk of automated attacks and widespread exploitation, especially in environments lacking adequate network defenses or monitoring. While the impact is medium severity, the ease of exploitation and potential for data compromise make this a critical concern for affected deployments.

Summary

CVE-2026-3135 identifies a SQL Injection vulnerability in the itsourcecode News Portal Project version 1.0, located in the /admin/add-category.php script. The vulnerability stems from insufficient input validation or sanitization of the 'Category' parameter, which is manipulated to inject arbitrary SQL commands into the backend database query. This flaw allows unauthenticated remote attackers to execute SQL statements, potentially leading to unauthorized data disclosure, modification, or deletion. The attack vector requires no privileges or user interaction, making it easier to exploit remotely. 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) reflects network attack vector, low attack complexity, no authentication or user interaction, and partial impact on confidentiality, integrity, and availability. Although no active exploitation has been reported, a public exploit is available, increasing the likelihood of future attacks. The vulnerability affects only version 1.0 of the News Portal Project, an open-source PHP-based content management system tailored for news websites. The lack of vendor patches or official fixes necessitates immediate mitigation by users. This vulnerability exemplifies common risks in web applications that do not properly sanitize user inputs before incorporating them into SQL queries, highlighting the importance of secure coding practices.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Mar 2026, 19:06 UTC

Technical details

References

Community reviews

Related threats