CVE-2013-3506
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 · uneditedcgi-bin/performance/perfchart.cgi in the Performance component in GroundWork Monitor Enterprise 6.7.0 does not properly restrict XML content, which allows remote attackers to execute arbitrary commands by creating a .shtml file and leveraging Server Side Includes (SSI) functionality.
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 perfchart.cgi script in GroundWork Monitor Enterprise 6.7.0 fails to properly restrict XML content, allowing remote attackers to inject malicious code. Attackers create .shtml files containing SSI directives that enable arbitrary command execution on the vulnerable server.
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= 6.7.0CVSS 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
- Partial
AV:N/AC:L/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.
-
Confirm GroundWork Monitor installationLocate the GroundWork Monitor installation directory and identify the installed version using package metadata, version files, or the admin interface. Common paths include /usr/local/groundwork/ or similar. Check for a VERSION or version.txt file in the installation directory.Affected if The installed version is exactly 6.7.0
-
Locate perfchart.cgi scriptSearch for the perfchart.cgi script in the web server's cgi-bin directory or within the GroundWork Monitor web application path, typically under /cgi-bin/ or /gwos/.Affected if The perfchart.cgi script exists and is accessible via the web server
-
Check web server SSI configurationInspect the web server configuration (Apache httpd.conf or equivalent) to determine if Server-Side Includes (SSI) are enabled, particularly for .shtml files. Look for 'AddType text/html .shtml', 'AddOutputFilter INCLUDES .shtml', or 'Options +Includes' directives.Affected if SSI is enabled and .shtml files are processed by the web server
-
Verify write access to web-accessible directoriesIdentify if user-contributed or externally supplied content can be written to directories served by the web server (such as upload directories or document roots), which would allow creation of .shtml files.Affected if Writable directories exist within the web server's document root that could accept .shtml file uploads
The system is affected if GroundWork Monitor version 6.7.0 is installed, the perfchart.cgi script is accessible, and the web server has SSI enabled with potential write access to web directories for .shtml file creation.
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 dataProperly restrict and sanitize XML content input in perfchart.cgi, and disable or properly sandbox SSI functionality to prevent command injection.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-3506 — 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-2013-3506 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