CVE-2007-0407
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 Operation/User.pm in Plain Black WebGUI before 7.3.5 (beta) allows remote attackers to inject arbitrary web script or HTML via the username parameter during anonymous registration, a different vector than CVE-2007-0308. NOTE: it is possible that a separate "WikiPage titles" issue was also fixed.
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 confidenceCross-site scripting (XSS) vulnerability in Operation/User.pm of Plain Black WebGUI allows remote attackers to inject arbitrary web script or HTML via the username parameter during anonymous registration. The flaw exists in versions prior to 7.3.5 (beta).
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= 6.3.0= 6.4.0= 6.5.0= 6.5.1= 6.5.2= 6.5.3= 6.5.4= 6.5.5= 6.5.6= 6.6.0= 6.6.1= 6.6.2CVSS 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.
-
Verify Plain Black WebGUI is installedLook for WebGUI installation directories or check for the presence of lib/WebGUI.pm or similar WebGUI core files in the web server document root or application directory.Affected if Plain Black WebGUI is not present on the system, then this CVE does not apply.
-
Determine the installed WebGUI versionCheck the version file or lib/WebGUI.pm for the version number. Typical locations include a VERSION file in the root directory or within the lib folder.Affected if The installed version is any of 6.3.0, 6.4.0, 6.5.0, 6.5.1, 6.5.2, 6.5.3, 6.5.4, 6.5.5, 6.5.6, 6.6.0, 6.6.1, or 6.6.2, or any version prior to 7.3.5.
-
Confirm anonymous registration is enabledInspect the WebGUI configuration file (usually webgui.conf or similar) for the allowAnonymousRegistration setting, or check the admin panel for user registration settings.Affected if Anonymous registration is enabled and the version is prior to 7.3.5, then the system is vulnerable.
-
Inspect Operation/User.pm for the vulnerabilityLocate the Operation/User.pm file in the lib/Operation directory and examine the anonymous registration handler code for the username parameter to see if it lacks proper input sanitization or output encoding.Affected if The code does not sanitize or encode the username parameter from anonymous registration, confirming the XSS vulnerability exists.
If Plain Black WebGUI version is prior to 7.3.5 and anonymous user registration is enabled, the system is affected by this 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 dataUpgrade Plain Black WebGUI to version 7.3.5 or later. Alternatively, apply input validation and output encoding to the username parameter in the anonymous registration functionality to sanitize user-supplied data.
- 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-0407 — 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-0407 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