Wireless Control SystemHardware / appliance · Cisco

CVE-2007-2035

HIGH · 7.8 CVSS v2.0 Published 2007-04-16
Fix available
A fix is available. Upgrade to after 4.0.95 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Cisco Wireless Control System (WCS) before 4.0.66.0 stores sensitive information under the web root with insufficient access control, which allows remote attackers to obtain network organization data via a direct request for files in certain directories, aka Bug ID CSCsg04301.

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 confidence

Cisco Wireless Control System (WCS) versions prior to 4.0.66.0 stores sensitive network organization data in directories under the web root with inadequate access controls, allowing unauthenticated remote attackers to directly request and retrieve this sensitive information via HTTP.

MitigationUpgrade Cisco WCS to version 4.0.66.0 or later, and review/audit the web root directory structure to ensure no sensitive data is stored in publicly accessible locations.

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
Wireless Control SystemHardware / appliance
Affected:<= 4.0.95

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Cisco WCS version
    Access the WCS web interface and look for the version information typically displayed in the login page or about section, or check via the WCS administrative console for the software version
    Affected if The installed version is any version prior to 4.0.66.0 (versions 4.0.0 through 4.0.65.x are affected; versions up to 4.0.95 are listed as affected per vendor advisory)
  2. Identify web root directory structure
    Locate the directory where WCS stores its web application files - this is typically the Apache Tomcat webroot or similar web serving directory used by WCS
    Affected if Sensitive network organization data (such as configuration files, network topology information, or device credentials) exists in directories under the web root that are accessible via HTTP
  3. Verify web access to sensitive directories
    Attempt to access common WCS web directories via HTTP without authentication - for example, try accessing directories that may contain configuration, database, or XML files directly through the browser
    Affected if Directories containing sensitive network organization data are directly accessible via HTTP without requiring authentication
  4. Check for unauthenticated file retrieval
    Use a web browser or HTTP tool to request known file types (such as XML, config, or database files) that may be stored in web-accessible WCS directories
    Affected if Sensitive files can be retrieved without any authentication credentials, indicating inadequate access controls on the web root directories

The environment is affected if Cisco WCS version is prior to 4.0.66.0 AND the web interface is accessible to users who could directly retrieve sensitive network organization data stored under the web root without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 4.0.95
Interim mitigation

Upgrade Cisco WCS to version 4.0.66.0 or later, and review/audit the web root directory structure to ensure no sensitive data is stored in publicly accessible locations.

Fix this in Wireless Control System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-2035 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-2035 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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