LiveActive security incident?Get immediate response
CVE Record

CVE-2007-1692: The default configuration of Microsoft Windows uses the Web Proxy Autodiscovery Protocol (WPAD) without sta...

The default configuration of Microsoft Windows uses the Web Proxy Autodiscovery Protocol (WPAD) without static WPAD entries, which might allow remote attackers to intercept web traffic by registering a proxy server using WINS or DNS, then responding to WPAD requests, as demonstrated using Internet Explorer. NOTE: it could be argued that if an attacker already has control over WINS/DNS, then web traffic could already be intercepted by modifying WINS or DNS records, so this would not cross privilege boundaries and would not be a vulnerability. It has also been reported that DHCP is an alternate attack vector.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This issue concerns Windows automatically looking for a web proxy through WPAD. If an attacker can influence local naming or address configuration services, users may be directed through an attacker-controlled proxy, exposing web traffic. The CVE record also notes debate over whether this crosses a privilege boundary. Exposure is most likely in Windows networks using automatic proxy discovery where WINS, DNS, or DHCP can be influenced by untrusted systems. Exact affected Windows versions are not identified in the provided CVE data. Treat this as a configuration and network-control risk, not a confirmed emergency. Prioritize environments with legacy Windows clients, WPAD enabled, or weak DNS, WINS, or DHCP administration controls. Mitigation focus: Review Microsoft KB 934864 and current Microsoft WPAD guidance.; Inventory Windows systems using automatic proxy discovery.; Use approved static proxy or WPAD configuration where required..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2007-1692 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.