CVE-2026-3406
SQL Injection in Online Art Gallery Shop Registration Handler
Publication date: 2026-03-02
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?
CVE-2026-3406 is a critical SQL injection vulnerability found in version 1.0 of the Online Art Gallery Shop Project by projectworlds. It specifically affects the file /admin/registration.php within the Registration Handler component. The vulnerability arises because the fname parameter is improperly handled and directly incorporated into SQL queries without adequate input validation or sanitization.
This flaw allows remote, unauthenticated attackers to inject malicious SQL code, enabling them to manipulate database queries. This can lead to unauthorized access to the database, data leakage, data modification or deletion, and potentially full system compromise.
How can this vulnerability impact me? :
The impact of this vulnerability is severe. Attackers can exploit it remotely without authentication to execute arbitrary SQL commands on the database.
- Unauthorized access to sensitive data stored in the database.
- Modification or deletion of data, potentially corrupting or destroying important information.
- Full system compromise, allowing attackers to control or disrupt the affected system.
- Potential service disruption due to malicious database manipulation.
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 vulnerable parameter `fname` in the affected file `/admin/registration.php` or `/admin/adminHome.php` for injection flaws using SQL injection techniques such as boolean-based blind, error-based, and time-based blind methods.'}, {'type': 'paragraph', 'content': 'Example payloads to test the `fname` parameter include:'}, {'type': 'list_item', 'content': "Boolean-based blind: fname=1' RLIKE (SELECT (CASE WHEN (8850=8850) THEN 1 ELSE 0x28 END)) AND 'tqAa'='tqAa"}, {'type': 'list_item', 'content': "Error-based: fname=1' AND GTID_SUBSET(CONCAT(0x716a767a71,(SELECT (ELT(5569=5569,1))),0x7162707871),5569) AND 'IvlC'='IvlC"}, {'type': 'list_item', 'content': "Time-based blind: fname=1' AND (SELECT 4541 FROM (SELECT(SLEEP(5)))ujMt) AND 'XYtn'='XYtn"}, {'type': 'paragraph', 'content': 'Tools like sqlmap can be used to automate detection and exploitation attempts against the `fname` parameter to confirm the presence of the vulnerability.'}, {'type': 'paragraph', 'content': 'Additionally, vulnerable targets can be identified using Google dorking with queries such as "inurl:admin/registration.php".'}] [2, 3]
What immediate steps should I take to mitigate this vulnerability?
[{'type': 'paragraph', 'content': 'Immediate mitigation steps for this SQL injection vulnerability include:'}, {'type': 'list_item', 'content': 'Use prepared statements with parameter binding to ensure user inputs are treated strictly as data and not executable SQL code.'}, {'type': 'list_item', 'content': 'Implement strict input validation and filtering to ensure inputs conform to expected formats and reject malicious input.'}, {'type': 'list_item', 'content': "Limit database user permissions to the minimum necessary, avoiding the use of high-privilege accounts such as 'root' or 'admin' for routine database operations."}, {'type': 'list_item', 'content': 'Conduct regular security audits of code and systems to detect and remediate vulnerabilities promptly.'}] [1, 2]