CVE-2007-3109
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 · uneditedThe CERN Image Map Dispatcher (htimage.exe) in Microsoft FrontPage allows remote attackers to determine the existence, and possibly partial contents, of arbitrary files under the web root via a relative pathname in the PATH_INFO.
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 CERN Image Map Dispatcher (htimage.exe) in Microsoft FrontPage allows remote attackers to determine the existence and possibly partial contents of arbitrary files under the web root via relative pathnames in the PATH_INFO parameter. This is an information disclosure vulnerability with low attack complexity, allowing directory traversal-like access to sensitive files.
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 dataall versionsall versionsCVSS 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
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:P/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 htimage.exe on the systemSearch the web root directories and system for the file htimage.exe or htimage.dll. Check common web directories such as C:\Inetpub\wwwroot\, C:\Program Files\Common Files\Microsoft Shared\, and any virtual website directories.Affected if htimage.exe or htimage.dll is found on the system under web-accessible paths
-
Verify FrontPage Server Extensions installationCheck for Microsoft FrontPage Server Extensions by examining Add/Remove Programs for 'Microsoft FrontPage Server Extensions' or check the registry under HKLM\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\ for installed versions.Affected if FrontPage Server Extensions are installed on the server
-
Check web server ISAPI/CGI filtersExamine the IIS metabase or web.config files for ISAPI filters or CGI extensions that reference htimage.exe or CERN-based image mapping components.Affected if An ISAPI filter or CGI extension handling .htimage or image map requests is enabled in the web server configuration
-
Test PATH_INFO parameter handlingSend an HTTP request to a suspected htimage.exe endpoint with a PATH_INFO parameter containing a relative path such as /../../windows/win.ini or /../../boot.ini and observe the response.Affected if The server returns file contents or reveals differences in HTTP response codes indicating successful directory traversal access to files outside the web root
A system is affected if htimage.exe exists and is accessible via a web server that processes PATH_INFO parameters without proper sanitization, allowing unauthorized file access.
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 dataRemove or disable the htimage.exe component if not required, and ensure the web server is properly configured to restrict file system access through PATH_INFO. Consider migrating away from FrontPage to modern web platforms to eliminate this legacy attack surface.
- Consultation4.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,912.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-3109 — 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-3109 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