CVE-2026-10265
SQL Injection in itsourcecode CMS 1.0
Publication date: 2026-06-01
Last updated on: 2026-06-01
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| itsourcecode | content_management_system | 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
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The SQL injection vulnerability in the itsourcecode Content Management System 1.0 allows unauthorized database access, data leakage, tampering, and potential system control. Such unauthorized access and data compromise can lead to violations of data protection regulations like GDPR and HIPAA, which mandate the protection of personal and sensitive information. Failure to secure the system against this vulnerability may result in non-compliance with these standards due to exposure or alteration of protected data.
Can you explain this vulnerability to me?
This vulnerability is a SQL injection issue found in the itsourcecode Content Management System version 1.0, specifically in the file /admin/edit_topic.php. It occurs because the 'topic_id' parameter does not properly sanitize user input before it is used in SQL queries.
An attacker can manipulate the 'topic_id' argument to inject malicious SQL code, which can be executed by the database. This can be done remotely and does not require authentication, as shown by a proof-of-concept using sqlmap.
How can this vulnerability impact me? :
Exploiting this vulnerability can allow attackers to gain unauthorized access to the database, leading to data leakage, data tampering, and potentially full system control.
It can also cause service interruptions and compromise the integrity and availability of the system.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL injection vulnerability in the 'topic_id' parameter of /admin/edit_topic.php can be detected by attempting to inject SQL code into the parameter and observing the response.
One common method is to use automated tools like sqlmap to test the endpoint for SQL injection vulnerabilities.
- Example sqlmap command: sqlmap -u "http://targetsite/admin/edit_topic.php?topic_id=1" --batch
- Alternatively, manual testing can be done by appending SQL payloads such as ' OR '1'='1 to the topic_id parameter and checking for unexpected behavior or database errors.
What immediate steps should I take to mitigate this vulnerability?
Immediate remediation steps include:
- Use prepared statements with parameterized queries to prevent SQL injection.
- Implement strict input validation and sanitization on the 'topic_id' parameter.
- Minimize database permissions to limit the impact of a potential exploit.
- Conduct regular security audits and code reviews to identify and fix vulnerabilities.