CVE-2010-4912 SQL injection vulnerability in shop.php in UCenter Home 2.0 allows remote attackers to execute arbitrary SQL commands via the shopid parameter in a view action.
High 7.5
Published
Updated
Check this codebase for CVE-2010-4912 and fix it if it is affected.
What it is: CVE-2010-4912 is a high-severity vulnerability in n/a, published on 8 Oct 2011.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-4912 exists.
Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2010-4912/ (Markdown: https://insights.sbomify.com/CVE-2010-4912/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2010-4912?
CVE-2010-4912 is a high-severity vulnerability in n/a, published on 8 Oct 2011.
Official description
SQL injection vulnerability in shop.php in UCenter Home 2.0 allows remote attackers to execute arbitrary SQL commands via the shopid parameter in a view action.
Weakness: CWE-89
Which versions are affected by CVE-2010-4912?
It affects 1 product.
Products include Discuz Ucenter Home.
How do I fix CVE-2010-4912?
No fix has been published for CVE-2010-4912 yet. Limit exposure of the affected software until one is available.
Is CVE-2010-4912 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-4912 exists.
Public exploit code: 1 Exploit-DB entry.
Sources
Also known as GHSA-3hpc-49f5-7pg8.