CVE-2026-3135
SQL Injection in itsourcecode News Portal /admin/add-category.php
Publication date: 2026-02-25
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| clive_21 | news_portal_project | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': 'CVE-2026-3135 is a critical SQL injection vulnerability found in the itsourcecode News Portal Project version 1.0, specifically in the file /admin/add-category.php.'}, {'type': 'paragraph', 'content': "The vulnerability arises from improper handling of the 'Category' argument, which allows an attacker to manipulate SQL commands due to insufficient neutralization of special characters."}, {'type': 'paragraph', 'content': 'This flaw allows attackers to inject malicious SQL code remotely without any authentication, enabling unauthorized database access.'}, {'type': 'paragraph', 'content': 'Exploitation is considered easy, and a proof-of-concept exploit is publicly available.'}] [1, 3]
How can this vulnerability impact me? :
Exploiting this vulnerability enables attackers to gain unauthorized access to the database.
- Retrieve sensitive information.
- Modify or delete data.
- Achieve full system control.
- Cause service disruption.
This impacts the confidentiality, integrity, and availability of the affected system, posing a severe risk to system security and business continuity.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': "This vulnerability can be detected by testing the 'category' parameter in the /admin/add-category.php file for SQL injection flaws."}, {'type': 'paragraph', 'content': "One method is to use time-based blind SQL injection payloads to confirm injection capability, such as the proof-of-concept payload: category=123123' AND (SELECT 4294 FROM (SELECT(SLEEP(5)))nSvx) AND 'GRoI'='GRoI."}, {'type': 'paragraph', 'content': 'Testing can be performed using tools like sqlmap targeting the vulnerable POST parameter.'}, {'type': 'list_item', 'content': "Use sqlmap with a POST request to /admin/add-category.php targeting the 'category' parameter."}, {'type': 'list_item', 'content': 'Manually test with payloads that cause delays or errors, such as the time-based blind SQL injection payload provided.'}, {'type': 'list_item', 'content': 'Use Google Dorking to identify vulnerable targets by searching for "inurl:admin/add-category.php".'}] [1, 3]
What immediate steps should I take to mitigate this vulnerability?
[{'type': 'paragraph', 'content': 'Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection.'}, {'type': 'paragraph', 'content': "Enforce strict input validation and filtering on the 'category' parameter to ensure only expected data formats are accepted."}, {'type': 'paragraph', 'content': 'Minimize database user permissions by avoiding the use of high-privilege accounts such as root or admin for routine database operations.'}, {'type': 'paragraph', 'content': 'Conduct regular security audits to detect and address vulnerabilities promptly.'}, {'type': 'paragraph', 'content': 'If possible, replace the affected component with an alternative product as no known countermeasures or patches are reported.'}] [1, 3, 2]