CVE-2007-0690
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 · uneditedmyEvent 1.6 allows remote attackers to obtain sensitive information via (1) a Log In action without a password to login.php, or an invalid (2) view[] or (3) monthno[] parameter to myevent.php, which reveals the path in various error messages.
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 confidencemyEvent 1.6 is vulnerable to path disclosure through improper error handling. Remote attackers can obtain sensitive file system path information by submitting malformed requests to login.php without a password, or by passing invalid view[] or monthno[] parameters to myevent.php. The application reveals full paths in error messages.
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= 1.6CVSS 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
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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 myEvent installation filesSearch the web root directory for myevent.php and login.php files. Check common paths like /var/www/html/, /www/, or C:\inetpub\wwwroot\ depending on the server OS.Affected if The files myevent.php and login.php exist, indicating myEvent is installed.
-
Identify the installed versionOpen myevent.php in a text editor or view the file properties to check the version comment/header inside the file.Affected if The version is 1.6 (or if version cannot be determined but the file exists, assume affected).
-
Test login.php for path disclosureSubmit an HTTP POST request to login.php with an empty or missing password parameter (e.g., using curl: curl -X POST http://target/login.php -d "username=admin").Affected if The error response contains a full file system path such as /home/user/public_html/myevent/ or C:\inetpub\wwwroot\myevent\.
-
Test myevent.php with invalid view parameterSubmit an HTTP GET request to myevent.php with an invalid view[] parameter (e.g., http://target/myevent.php?view[]=invalid).Affected if The error response reveals a full file system path.
-
Test myevent.php with invalid monthno parameterSubmit an HTTP GET request to myevent.php with an invalid monthno[] parameter (e.g., http://target/myevent.php?monthno[]=invalid).Affected if The error response reveals a full file system path.
If myEvent 1.6 is installed and any of the tested endpoints return error messages containing full local file paths, the environment is affected by this path disclosure 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 proper error handling that displays generic error messages to users instead of detailed stack traces or path information. Validate and sanitize all user input before processing.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-0690 — 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-0690 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