CVE-2013-3510
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 · uneditedMultiple SQL injection vulnerabilities in GroundWork Monitor Enterprise 6.7.0 allow remote authenticated users to execute arbitrary SQL commands via (1) nedi/html/System-Export.php, (2) nedi/html/Devices-List.php, or (3) the Noma component.
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 confidenceMultiple SQL injection vulnerabilities in GroundWork Monitor Enterprise 6.7.0 allow remote authenticated users to execute arbitrary SQL commands via three attack vectors: nedi/html/System-Export.php, nedi/html/Devices-List.php, and the Noma component. The CVSS 6.5 indicates network-exploitable flaws requiring authentication but with moderate attack complexity.
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
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:S/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 GroundWork Monitor installation and versionLocate the GroundWork Monitor installation directory and check the version file or about page, typically found in the web interface or installation logsAffected if The installed version is exactly 6.7.0
-
Verify presence of vulnerable nedi componentCheck for the existence of the nedi/html/ directory under the GroundWork web root and list its contentsAffected if The directory nedi/html/ exists and contains System-Export.php and Devices-List.php
-
Inspect System-Export.php for injection vulnerabilityExamine the file nedi/html/System-Export.php for unsanitized SQL query parameters; look for direct use of $_GET or $_POST variables in SQL statements without prepared statements or escapingAffected if The file contains SQL queries that incorporate user-supplied parameters without parameterization
-
Inspect Devices-List.php for injection vulnerabilityExamine the file nedi/html/Devices-List.php for unsanitized SQL query parameters; look for direct use of $_GET or $_POST variables in SQL statements without prepared statements or escapingAffected if The file contains SQL queries that incorporate user-supplied parameters without parameterization
-
Verify Noma component presenceLocate the Noma component within the GroundWork installation, typically in the web directory structure, and inspect its PHP files for unsanitized SQL queriesAffected if The Noma component is installed and contains PHP files with direct SQL query construction using user input
A system is affected if it runs GroundWork Monitor Enterprise version 6.7.0 with the nedi/html/System-Export.php, nedi/html/Devices-List.php, or Noma component accessible via the web interface.
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 dataRemediate by implementing parameterized queries or prepared statements in the affected PHP files (System-Export.php, Devices-List.php) and Noma component to neutralize SQL injection vectors, or apply vendor-supplied patches if available.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-3510 — 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-3510 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