CVE-2026-3758
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA weakness has been identified in projectworlds Online Art Gallery Shop 1.0. Affected by this issue is some unknown functionality of the file /admin/adminHome.php. This manipulation of the argument Info causes sql injection. Remote exploitation of the attack is possible. The exploit has been made available to the public and could be used for attacks.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA SQL injection vulnerability exists in the /admin/adminHome.php file of projectworlds Online Art Gallery Shop 1.0. The 'Info' parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject arbitrary SQL commands. With a CVSS score of 9.8 (Critical) and a public exploit available, this vulnerability poses a severe risk as it could allow unauthenticated or authenticated attackers to exfiltrate, modify, or delete database contents.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed application versionLocate and examine the application files to confirm it is Projectworlds Online Art Gallery Shop version 1.0. Check for version indicators in source files, README, or configuration files.Affected if The application is Projectworlds Online Art Gallery Shop version 1.0
-
Verify the vulnerable file existsCheck for the presence of the file /admin/adminHome.php in the web root directory.Affected if The file adminHome.php exists in the /admin/ directory
-
Confirm admin interface accessibilityAttempt to access the /admin/ directory via HTTP/HTTPS to determine if the administrative interface is reachable.Affected if The /admin/ endpoint is accessible and the application is running
-
Check Info parameter handling in the codeExamine the adminHome.php source code and locate the 'Info' parameter usage within SQL query contexts. Look for unsanitized variable insertion into SQL statements.Affected if The 'Info' parameter is used in SQL queries without parameterized statements or input sanitization
Your environment is affected if you are running Projectworlds Online Art Gallery Shop 1.0 with the adminHome.php file present and the admin interface accessible, where the 'Info' parameter is processed without proper SQL injection protection.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace dynamic SQL queries with parameterized queries or prepared statements in adminHome.php, then conduct a comprehensive code audit of the entire application to identify and remediate similar SQL injection vulnerabilities in other input-handling code paths.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3758 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-3758 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data