CVE-2009-3066 Multiple cross-site scripting (XSS) vulnerabilities in PropertyWatchScript.com Property Watch 2.0 allow remote attackers to inject arbitrary
Medium 4.3
Published
Updated
Check this codebase for CVE-2009-3066 and fix it if it is affected.
What it is: CVE-2009-3066 is a medium-severity vulnerability in n/a, published on 3 Sep 2009.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-3066 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-2009-3066/ (Markdown: https://insights.sbomify.com/CVE-2009-3066/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2009-3066?
CVE-2009-3066 is a medium-severity vulnerability in n/a, published on 3 Sep 2009.
Official description
Multiple cross-site scripting (XSS) vulnerabilities in PropertyWatchScript.com Property Watch 2.0 allow remote attackers to inject arbitrary web script or HTML via the (1) videoid parameter to tools/email.php and (2) redirect parameter to tools/login.php.
Weakness: CWE-79
Which versions are affected by CVE-2009-3066?
It affects 1 product.
Products include Propertywatchscript Property Watch.
How do I fix CVE-2009-3066?
No fix has been published for CVE-2009-3066 yet. Limit exposure of the affected software until one is available.
Is CVE-2009-3066 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-3066 exists.
Public exploit code: 2 Exploit-DB entries.
Sources
Also known as GHSA-p56p-c4j5-395j.