CVE-2007-0477
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-site scripting (XSS) vulnerability in Openads 2.0.x before 2.0.10, 2.3 before 2.3.31 (aka Max Media Manager before 0.3.31-alpha-pr2), and phpAdsNew/phpPgAds before 2.0.9-pr1 allows remote attackers to inject arbitrary web script or HTML via (1) the keyword parameter in admin-search.php and (2) affiliate-search.php. NOTE: this issue may overlap CVE-2007-0363.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceReflected XSS vulnerability in Openads/phpAdsNew advertising software allows remote attackers to inject arbitrary JavaScript/HTML via the keyword parameter in admin-search.php and affiliate-search.php. User-supplied input in the keyword search field is not properly sanitized before being reflected back in the page output.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2.3.30CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Openads/phpAdsNew installationLocate the software by searching for admin-search.php or affiliate-search.php in your web directory, or look for the Openads/phpAdsNew administrative interface.Affected if Openads or phpAdsNew is installed on the server
-
Identify the installed versionCheck the version file typically found in the Openads root directory, often named VERSION or in a config file that displays the software version.Affected if The installed version is Openads 2.3.30 specifically
-
Verify vulnerable files existCheck for the presence of admin-search.php and affiliate-search.php in the admin and affiliate directories of your Openads installation.Affected if Both admin-search.php and affiliate-search.php exist in the expected paths
-
Confirm admin/affiliate interface is accessibleVerify that the administrative interface is accessible over the network, as this is required for the keyword parameter to be processed.Affected if The admin or affiliate search functionality is reachable via HTTP/HTTPS
-
Test keyword parameter for unsanitized reflectionSubmit a test XSS payload in the keyword parameter to the affected search pages and verify if the input is reflected without proper encoding. For example, submit: keyword=<script>alert('XSS')</script>Affected if The keyword parameter reflects the input back without HTML encoding or sanitization
A user is affected if Openads version 2.3.30 is installed and the admin-search.php or affiliate-search.php files are accessible, with the keyword parameter reflecting unsanitized user input.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to Openads 2.0.10+, 2.3.31+, or phpAdsNew/phpPgAds 2.0.9-pr1 or later, which contain patches for proper input validation on the keyword parameter in both affected files.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-0477 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2007-0477 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data