CVE-2007-1901 SonicBB 1.0 allows remote attackers to obtain sensitive information via the (1) by[] parameter to search.php, (2) p[] parameter to viewforum
Medium 4.3
Published
Updated
Check this codebase for CVE-2007-1901 and fix it if it is affected.
What it is: CVE-2007-1901 is a medium-severity vulnerability in n/a, published on 14 May 2007.
Exploitation: There is no known exploitation of CVE-2007-1901 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-2007-1901/ (Markdown: https://insights.sbomify.com/CVE-2007-1901/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2007-1901?
CVE-2007-1901 is a medium-severity vulnerability in n/a, published on 14 May 2007.
Official description
SonicBB 1.0 allows remote attackers to obtain sensitive information via the (1) by[] parameter to search.php, (2) p[] parameter to viewforum.php, and the (3) id parameter to (a) viewforum.php or (b) members.php, which reveal the installation path in the resulting error message.
Which versions are affected by CVE-2007-1901?
It affects 1 product.
Products include Sonicbb Sonicbb.
How do I fix CVE-2007-1901?
No fix has been published for CVE-2007-1901 yet. Limit exposure of the affected software until one is available.
Is CVE-2007-1901 being exploited?
There is no known exploitation of CVE-2007-1901 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-82x5-q33g-px2w.