CVE-2011-4518
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 · uneditedDirectory traversal vulnerability in the PmWebDir object in the web server in MICROSYS PROMOTIC before 8.1.5 allows remote attackers to read arbitrary files via unspecified vectors.
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 confidenceThis is a directory traversal vulnerability in the PmWebDir object of the PROMOTIC web server component, present in versions before 8.1.5. The flaw allows remote attackers to escape the intended web root directory and read arbitrary files on the system by manipulating file paths, likely using "../" sequences in HTTP requests.
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<= 8.1.4= 8.0.0= 8.0.1= 8.0.2= 8.0.3= 8.0.4= 8.0.5= 8.0.6= 8.0.7= 8.0.8= 8.0.9= 8.0.10CVSS 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
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/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.
-
Identify PROMOTIC installationCheck the system for PROMOTIC installation. Look for the installation directory (commonly C:\Program Files\Microsys\Promotic or similar), or check Windows Programs and Features for Microsys Promotic.Affected if PROMOTIC software is installed on the system
-
Determine installed PROMOTIC versionLocate the version information. Check the installation directory for a version file, or right-click on the Promotic executable and view Properties > Details. Common paths include C:\Program Files\Microsys\Promotic\Pm.exe or within the application folder.Affected if The installed version is 8.1.4 or lower, or any of these versions: 8.0.0, 8.0.1, 8.0.2, 8.0.3, 8.0.4, 8.0.5, 8.0.6, 8.0.7, 8.0.8, 8.0.9, or 8.0.10
-
Verify PmWebDir component is in useExamine the PROMOTIC application configuration files (typically with .pra or .prj extension) for the PmWebDir object. This object is used for web server functionality. Check configuration files for entries containing 'PmWebDir' or web directory settings.Affected if The PmWebDir object is configured and enabled in the PROMOTIC application configuration
-
Check web server exposureReview network configuration to determine if the PROMOTIC web server is accessible externally. Check firewall rules and binding addresses in the PmWebDir settings to see if the web interface listens on public-facing network interfaces.Affected if The PmWebDir web server is bound to a publicly accessible IP address or exposed through firewall rules
You are affected if PROMOTIC with a vulnerable version (8.1.4 or lower, or any 8.0.x version listed) is installed with the PmWebDir component enabled and accessible.
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 PROMOTIC to version 8.1.5 or later, which contains the fix for this vulnerability. Additionally, implement strict input validation on the PmWebDir component to sanitize path references and ensure proper access controls on the web server.
- Consultation2.0 h
- Implementation3.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,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-4518 — 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-2011-4518 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