CVE-2006-1561 SQL injection vulnerability in index.php in vscripts (aka Kuba Kunkiewicz) [V]Book (aka VBook) 2.0 allows remote attackers to execute arbitr
Medium 5.1
Published
Updated
Check this codebase for CVE-2006-1561 and fix it if it is affected.
What it is: CVE-2006-1561 is a medium-severity vulnerability in n/a, published on 31 Mar 2006.
Exploitation: There is no known exploitation of CVE-2006-1561 in the wild and no public exploit code.
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-2006-1561/ (Markdown: https://insights.sbomify.com/CVE-2006-1561/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2006-1561?
CVE-2006-1561 is a medium-severity vulnerability in n/a, published on 31 Mar 2006.
Official description
SQL injection vulnerability in index.php in vscripts (aka Kuba Kunkiewicz) [V]Book (aka VBook) 2.0 allows remote attackers to execute arbitrary SQL commands via the x parameter.
Which versions are affected by CVE-2006-1561?
It affects 1 product.
Products include Vscripts Vbook.
How do I fix CVE-2006-1561?
No fix has been published for CVE-2006-1561 yet. Limit exposure of the affected software until one is available.
Is CVE-2006-1561 being exploited?
There is no known exploitation of CVE-2006-1561 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-vc98-h6mj-8cgf.