CVE-2007-0194
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 · uneditedadmin.php in MKPortal M1.1 RC1 allows remote attackers to obtain sensitive information via a direct request with an MK_PATH=1 query string, which reveals the path in an error message.
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 confidenceThe admin.php script in MKPortal M1.1 RC1 contains an information disclosure vulnerability where a remote attacker can obtain the server's full filesystem path by appending the query string MK_PATH=1 to a direct request for admin.php. The application reveals this sensitive path information within an error message.
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.1_rc1CVSS 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
- Complete
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:C/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.
-
Verify MKPortal installation existsLocate the MKPortal installation directory on the web server and confirm the presence of admin.phpAffected if MKPortal is installed and admin.php is accessible
-
Confirm the installed version is 1.1_rc1Check the version identifier in MKPortal's version file, about page, or metadataAffected if The installed version is exactly 1.1_rc1 (no other version)
-
Locate the admin.php scriptNavigate to the MKPortal root directory and verify admin.php existsAffected if admin.php is present in the MKPortal installation
-
Test for the MK_PATH parameter vulnerabilitySend an HTTP request to admin.php with the query string MK_PATH=1 (e.g., https://site/path/admin.php?MK_PATH=1) and observe if the full server filesystem path appears in the responseAffected if The response contains the absolute server filesystem path in an error or informational message
-
Check if PHP error display is enabledReview the PHP configuration (php.ini) or the application's error handling settings to determine if display_errors is set to OnAffected if PHP display_errors is enabled, allowing the path disclosure to be visible to attackers
The environment is affected if MKPortal version 1.1_rc1 is installed, admin.php is accessible, and the MK_PATH=1 parameter reveals the server's full filesystem path in the response.
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 dataDisable PHP error display and configure proper error handling in the application's configuration to prevent path disclosure, or apply a patch from the vendor to fix the specific code path in admin.php that handles the MK_PATH parameter.
- Consultation2.0 h
- Implementation1.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-0194 — 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-0194 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