CVE-2006-4028 Multiple unspecified vulnerabilities in WordPress before 2.0.4 have unknown impact and remote attack vectors.
Critical 10.0
Published
Updated
Check this codebase for CVE-2006-4028 and fix it if it is affected.
What it is: CVE-2006-4028 is a critical vulnerability in Wordpress Wordpress, published on 9 Aug 2006.
Exploitation: There is no known exploitation of CVE-2006-4028 in the wild and no public exploit code.
Affected product: Wordpress Wordpress. 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-4028/ (Markdown: https://insights.sbomify.com/CVE-2006-4028/index.md)
- Exploited in the wild
- Not known
- Fix
- Available
What is CVE-2006-4028?
CVE-2006-4028 is a critical vulnerability in Wordpress Wordpress, published on 9 Aug 2006.
Official description
Multiple unspecified vulnerabilities in WordPress before 2.0.4 have unknown impact and remote attack vectors. NOTE: due to lack of details, it is not clear how these issues are different from CVE-2006-3389 and CVE-2006-3390, although it is likely that 2.0.4 addresses an unspecified issue related to "Anyone can register" functionality (user registration for guests).
Which versions are affected by CVE-2006-4028?
It affects 1 product.
Products include Wordpress Wordpress.
How do I fix CVE-2006-4028?
Upgrade to a fixed version.
Is CVE-2006-4028 being exploited?
There is no known exploitation of CVE-2006-4028 in the wild and no public exploit code.
Other vulnerabilities in Wordpress Wordpress
Sources
Also known as DEBIAN-CVE-2006-4028, GHSA-5fp4-c42w-xqf3.