Security readout for executives and security teams
pycsw had a SQL injection flaw in versions before 2.0.2, 1.10.5, and 1.8.6. An attacker could read data from tables the pycsw database account can access. On PostgreSQL, sources state database changes may also be possible. Business risk depends on whether pycsw is internet-facing and what that database account can access. Organizations running pycsw before 2.0.2, 1.10.5, or 1.8.6 are exposed. Risk is highest where pycsw is externally reachable or the configured database user can access sensitive or non-pycsw tables. Prioritize remediation for internet-facing pycsw deployments and environments where the database account has broad privileges. Treat as high urgency when catalog data is sensitive or PostgreSQL write-capable access exists. Mitigation focus: Upgrade pycsw to 2.0.2, 1.10.5, 1.8.6, or a later fixed release.; If upgrading is delayed, review upstream patch guidance and vendor release notes.; Restrict the pycsw database account to only required tables and operations..
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2016-8640 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/geopython/pycsw/pull/474/filesCVE reference · x_refsource_CONFIRM
- https://patch-diff.githubusercontent.com/raw/geopython/pycsw/pull/474.patchCVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.