CVE-2026-3758
SQL Injection in Projectworlds Online Art Gallery Shop Admin Panel
Publication date: 2026-03-08
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 |
|---|---|---|
| projectworlds | online_art_gallery_shop | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': "CVE-2026-3758 is a critical SQL injection vulnerability found in version 1.0 of the Online Art Gallery Shop by projectworlds, specifically in the /admin/adminHome.php file. The vulnerability arises from improper handling and inadequate validation of the 'info' parameter, which is used directly in SQL queries without sufficient input sanitization. This flaw allows attackers to inject malicious SQL code remotely without authentication, enabling them to manipulate database queries."}, {'type': 'paragraph', 'content': 'The injection can be performed using various SQL injection techniques such as boolean-based blind, error-based, and time-based blind methods. Exploiting this vulnerability can lead to unauthorized access to the database, data leakage, modification, deletion, and potentially full system control.'}] [1, 3, 4]
How can this vulnerability impact me? :
This vulnerability can severely impact the confidentiality, integrity, and availability of your system. An attacker can remotely exploit the flaw without any authentication to gain unauthorized access to your database.
- Retrieve sensitive information from the database.
- Modify or delete data, potentially causing data loss or corruption.
- Gain full control over the system, leading to further exploitation.
- Cause service disruption, affecting 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 SQL injection vulnerability can be detected by testing the /admin/adminHome.php endpoint for improper handling of the 'info' parameter using SQL injection techniques."}, {'type': 'paragraph', 'content': 'Example payloads to test include boolean-based blind, error-based, and time-based blind SQL injection methods such as:'}, {'type': 'list_item', 'content': "Boolean-based blind: info=1' RLIKE (SELECT (CASE WHEN (1202=1202) THEN 1 ELSE 0x28 END))--"}, {'type': 'list_item', 'content': "Error-based: info=1' AND GTID_SUBSET(CONCAT(0x716b707671,(SELECT (ELT(9351=9351,1))),0x716a786b71),9351)--"}, {'type': 'list_item', 'content': "Time-based blind: info=1' AND (SELECT 5591 FROM (SELECT(SLEEP(5)))wHVo)--"}, {'type': 'paragraph', 'content': 'Additionally, vulnerable targets can be identified using Google hacking by searching for URLs containing "admin/adminHome.php".'}] [1, 4]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include:
- Use prepared statements with parameter binding to separate SQL code from user input, preventing injection.
- Implement strict input validation and filtering to ensure inputs conform to expected formats.
- Minimize database user permissions by avoiding high-privilege accounts (such as root or admin) for routine operations.
- Conduct regular security audits to detect and address vulnerabilities promptly.
If possible, replace the affected software with an alternative product as no known countermeasures or official patches have been documented.