CVE-2007-2432
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 utilities/search.asp in nukedit 4.9.7b allows remote attackers to inject arbitrary web script or HTML via the terms parameter. NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.
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 · moderate confidenceReflected XSS vulnerability in nukedit 4.9.7b's search functionality (utilities/search.asp). The 'terms' parameter accepts unsanitized user input that is reflected back in the HTTP response without proper output encoding, allowing injection of arbitrary HTML or script tags that execute in victim browsers.
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= 4.9.7bCVSS 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.
-
Locate Nukedit installationSearch for the nukedit installation directory on the web server, typically found in web root folders such as /nukedit/, /cms/, or as the web root itself. Check for presence of Nukedit files and directories.Affected if Nukedit is not installed on the system.
-
Identify Nukedit versionLook for a version indicator in Nukedit. Check the main index page source, a version file in the installation directory, or the HTTP server banner. Common locations include a footer in the HTML or a version.txt file.Affected if The installed version is Nukedit 4.9.7b.
-
Verify vulnerable script existsConfirm that the file utilities/search.asp exists within the Nukedit installation directory. Check the path: /nukedit/utilities/search.asp or the equivalent path within your web root.Affected if The file utilities/search.asp exists in the Nukedit installation.
-
Check for 'terms' parameter supportExamine the utilities/search.asp file to verify it accepts a 'terms' parameter in HTTP GET or POST requests. This can be done by reviewing the source code or testing the endpoint with a test query.Affected if The search.asp script accepts and processes a 'terms' parameter without sanitization.
If Nukedit 4.9.7b is installed with utilities/search.asp present and the 'terms' parameter is processed without output encoding, the environment is affected by this reflected XSS vulnerability.
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 dataImplement input validation and output encoding on the 'terms' parameter in utilities/search.asp. All user-supplied input should be validated against an allowlist and properly escaped before being rendered in HTML.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-2432 — 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-2432 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