CVE-2026-3757
SQL Injection in projectworlds Online Art Gallery Shop
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-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)?:
I don't know
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': "CVE-2026-3757 is a critical SQL injection vulnerability found in projectworlds Online Art Gallery Shop version 1.0. It exists in an unknown functionality of the file accessed via the URL parameter '/?pass=1', specifically through manipulation of the 'fnm' argument."}, {'type': 'paragraph', 'content': "The vulnerability occurs because the application does not properly sanitize or validate the 'fnm' parameter, allowing attackers to inject malicious SQL code. This improper neutralization of special elements used in SQL commands corresponds to CWE-89."}, {'type': 'paragraph', 'content': 'The attack can be launched remotely without any authentication, making it highly accessible. Exploiting this flaw allows attackers to manipulate database queries arbitrarily.'}] [1, 2, 3]
How can this vulnerability impact me? :
[{'type': 'paragraph', 'content': "This vulnerability can have severe impacts on the affected system's confidentiality, integrity, and availability."}, {'type': 'list_item', 'content': 'Attackers can gain unauthorized access to the database.'}, {'type': 'list_item', 'content': 'Sensitive data leakage may occur.'}, {'type': 'list_item', 'content': 'Attackers can tamper with data, including unauthorized modification or deletion of records.'}, {'type': 'list_item', 'content': 'Full system compromise and potential service disruption are possible.'}] [1, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'The vulnerability can be detected by testing the URL parameter `/?pass=1` with the `fnm` argument for SQL injection flaws. This involves sending crafted inputs to the `fnm` parameter to see if SQL commands can be injected and executed.'}, {'type': 'paragraph', 'content': 'Common detection methods include using automated SQL injection scanners or manual testing with tools like sqlmap targeting the URL parameter `/?pass=1&fnm=<payload>`.'}, {'type': 'list_item', 'content': 'Example sqlmap command: sqlmap -u "http://target/?pass=1&fnm=test" --batch'}, {'type': 'list_item', 'content': "Manual testing can include injecting typical SQL payloads such as `' OR '1'='1` or `' UNION SELECT NULL--` into the `fnm` parameter and observing the response for SQL errors or unexpected behavior."}] [1, 2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the affected software with an alternative product if possible, as no known countermeasures are documented.
If replacement is not feasible, apply the following measures:
- Use prepared statements (parameterized queries) to ensure user inputs are treated as data and not executable SQL code.
- Implement strict input validation and filtering on the `fnm` parameter to ensure inputs conform to expected formats.
- Limit database user permissions to the minimum necessary, avoiding high-privilege accounts for routine operations.
- Conduct regular security audits of code and systems to detect and remediate vulnerabilities promptly.