Security readout for executives and security teams
Plain-English summary
CVE-2017-14600 describes an SQL injection issue in Pragyan CMS v3.0 that could expose information. The public record does not provide CVSS, confirmed affected CPEs, or a named patch, so urgency depends on whether the organization still runs Pragyan CMS v3.0.
Executive priority
Prioritize discovery first. This is an older CMS SQL injection with incomplete severity data, but any internet-exposed Pragyan CMS v3.0 system should be treated as a remediation candidate because information disclosure is reported.
Technical view
The CVE description reports an error-based SQL injection in Pragyan CMS v3.0, in cms/admin.lib.php through the $_GET['del_black'] input, resulting in information disclosure. The bundled metadata has no CWE, CVSS, or structured affected product data beyond the narrative description.
Likely exposure
Exposure is likely limited to organizations running Pragyan CMS v3.0, particularly deployments with accessible administrative functionality. The source bundle does not identify other versions or products.
Exploitation context
The CVE is not listed as KEV in the supplied bundle, and no cited source confirms active exploitation. The GitHub issue is the only vulnerability reference provided.
Researcher notes
Evidence is sparse: one CVE description and one GitHub issue reference. Do not infer broader version impact, exploit maturity, or patch availability from the supplied data alone. Validate only in authorized environments and avoid destructive testing.
Mitigation direction
- Identify any Pragyan CMS v3.0 deployments, especially admin-facing instances.
- Check the linked project issue and vendor/project guidance for fixes or upgrade direction.
- Restrict administrative access while remediation status is confirmed.
- Review database account privileges for least-privilege configuration.
- Retire or isolate unsupported Pragyan CMS deployments where no fix is available.
Validation and detection
- Inventory web assets for Pragyan CMS v3.0 installations.
- Confirm whether cms/admin.lib.php exists in deployed code.
- Review access logs for suspicious admin requests and SQL error responses.
- Check dependency or source history against the linked project issue.
- Document remediation status for each confirmed deployment.
Public sources used
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.
Database 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-2017-14600 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/delta/pragyan/issues/228CVE reference · x_refsource_MISC
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.