CVE-2026-10874
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 vulnerability was identified in projectworlds Online Art Gallery Shop Project 1.0. The affected element is an unknown function of the file /admin/adminHome.php. The manipulation of the argument social_insta leads to sql injection. The attack may be initiated remotely. The exploit is publicly available and might be used.
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 · high confidenceSQL injection vulnerability in projectworlds Online Art Gallery Shop Project 1.0 allows remote attackers to inject malicious SQL queries through the unsanitized social_insta parameter in the /admin/adminHome.php file.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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 productLocate the Online Art Gallery Shop Project application in your environment. Check for files or directories related to this project.Affected if The product is present on the system
-
Verify the product versionCheck the version of the installed projectworlds Online Art Gallery Shop Project. Look for version identifiers in source files, configuration, or the application itself.Affected if The installed version is 1.0
-
Confirm adminHome.php existsVerify the presence of the file /admin/adminHome.php in the web application root directory.Affected if The file adminHome.php exists in the admin directory
-
Check social_insta parameter handlingInspect the adminHome.php file and locate the code that processes the social_insta parameter. Determine if it uses dynamic SQL queries or parameterized queries.Affected if The code uses direct string concatenation with the social_insta parameter in SQL queries without prepared statements or parameter binding
-
Assess network accessibilityDetermine if the /admin/adminHome.php endpoint is accessible from the network. Check firewall rules, authentication requirements, and network exposure.Affected if The vulnerable endpoint is accessible remotely without additional security controls
A user is affected if they have projectworlds Online Art Gallery Shop Project version 1.0 installed with the admin/adminHome.php file present and the social_insta parameter processed via unprotected dynamic SQL queries.
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 dataImplement parameterized queries (prepared statements) for all database interactions involving user-supplied input, particularly the social_insta parameter, and conduct a broader code audit to identify and remediate similar injection points.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10874 — 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-10874 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