S4E just found a high-severity finding from cve-2026-42945 scanner (version based)
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
critical·Product Based Web Vulnerabilities·Updated May 5, 2026

CVE-2026-42031 Scanner

CVE-2026-42031 Scanner - SQL Injection vulnerability in CKAN

Est. Time~10 seconds
Scan TypeSingle Scan
Targetsurl
CostFree
3.2k
Times Used
continuous scan runs
6k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
CVECVE-2026-42031
8.3
CVSShigh
Exploitable remotely over the internet · no authentication required.

CKAN is an open-source DMS (data management system) for powering data hubs and data portals. Prior to 2.10.10 and 2.11.5, a vulnerability in datastore_search_sql allowed attackers to inject SQL in order to gain access to private resources and PostgreSQL system information This vulnerability is fixed in 2.10.10 and 2.11.5.

Attack Vector
Network
Privileges Req.
None
User Interaction
None
Affected
ckanby ckan
>= 2.11.0, < 2.11.5
Updated Sep 10, 2026View on NVD →
Detail

CKAN is a popular open-source data management system used for creating and managing open data portals. Organizations around the world, including governments and companies, use CKAN to manage their open data programs effectively. Its flexible architecture allows users to publish, share, and query a diverse range of datasets, making it a preferred choice for open data solutions. The platform supports a variety of enhancements through extensions, allowing for further customization and adaptability to different needs. Its intuitive interface makes data accessible to non-technical users, facilitating data transparency and insight generation. CKAN is deployed on numerous platforms, providing scalability for both small and extensive datasets.

SQL Injection is a critical vulnerability that allows attackers to interfere with the queries that an application makes to its database. This unauthenticated vulnerability has been identified in CKAN's 'datastore_search_sql' API endpoint. Such vulnerabilities often result from improperly sanitized inputs allowing attackers to execute arbitrary SQL code. If exploited, the vulnerability can lead to unauthorized data access, data exfiltration, or potential data modification due to the injection of rogue SQL statements. As this flaw requires no credentials, its ease of exploitation makes it especially risky. Overall, it highlights the need for secure coding practices and regular security assessments.

The vulnerability resides in the 'datastore_search_sql' API endpoint, which is part of CKAN's data management framework. The endpoint fails to sufficiently sanitize SQL queries, allowing attackers to craft inputs that execute arbitrary SQL commands. Through this lack of input validation, attackers can exploit the API to inject SQL code, potentially extracting sensitive information. The flaw primarily affects PostgreSQL databases, often used by CKAN deployments, giving attackers access to valuable and sensitive data such as system catalog tables and private resources. Proper exploitation could also target user credentials, putting data integrity at further risk. Remediation involves updating CKAN to secure releases and implementing stricter input validation.

If this SQL injection vulnerability is exploited by an attacker, it can have various severe consequences. The unauthorized extraction of sensitive and confidential data from the database poses a significant privacy and data protection risk. Compromised credentials may lead to additional unauthorized access and potential misuse of the application. Furthermore, any unauthorized modifications to the database through injected SQL commands could damage data integrity and affect system operations. Given the database access level afforded by the vulnerability, the effects of such an attack can be extensive if mitigations are not promptly applied.

REFERENCES

Solution Advice
  • Upgrade CKAN to version 2.10.10 or 2.11.5 or later.
  • Enforce rigorous input validation and sanitization on all SQL queries.
  • Apply principle of least privilege to database access.
  • Regularly audit and monitor application logs for suspicious activities.
  • Consider using parameterized queries to prevent SQL injections.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

11,000+ scanners. Free to start. No credit card required.