CVE-2014-3006
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 · uneditedSitepark Information Enterprise Server (IES) 2.9 before 2.9.6, when upgraded from an earlier version, does not properly restrict access, which allows remote attackers to change the manager account password and obtain sensitive information via a request to install/.
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 · moderate confidenceSitepark Information Enterprise Server (IES) 2.9 before 2.9.6 has an improper access control vulnerability in the upgrade path. When the software is upgraded from an earlier version, the install/ directory remains accessible without authentication, allowing remote attackers to reset the manager account password and exfiltrate sensitive information.
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= 2.9CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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.
-
Identify Sitepark IES installationLocate the Sitepark Information Enterprise Server installation directory on the systemAffected if The software is installed but version cannot be determined or is 2.9.x before 2.9.6
-
Determine installed versionCheck the installed version of Sitepark IES against the affected range (2.9 before 2.9.6)Affected if Installed version is 2.9.x where x is less than 6 (e.g., 2.9.0 through 2.9.5)
-
Verify install directory existsCheck for the presence of an install/ or similar upgrade installation directory within the Sitepark web rootAffected if The install/ directory exists on the system
-
Test install directory accessAttempt to access the install/ directory path via HTTP/HTTPS without authentication credentialsAffected if The install/ directory is accessible without any authentication required
-
Check upgrade historyReview system logs or configuration to determine if the installation was upgraded from an earlier version of Sitepark IESAffected if The system was upgraded from a version prior to 2.9 and retains the vulnerable install/ directory
A user is affected if Sitepark IES version 2.9.x (before 2.9.6) is installed and the install/ directory remains accessible without authentication, particularly on systems that were upgraded from earlier versions.
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 dataUpgrade to Sitepark IES version 2.9.6 or later which properly restricts access to the install/ directory. Until patched, network-level blocking of the install/ path is recommended as a compensating control.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.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 $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-3006 — 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-2014-3006 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