LiveActive security incident?Get immediate response
CVE Record

CVE-2023-39806: iCMS v7.0.16 was discovered to contain a SQL injection vulnerability via the bakupdata function.

iCMS v7.0.16 was discovered to contain a SQL injection vulnerability via the bakupdata function.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2023-39806 is a reported SQL injection issue in iCMS v7.0.16, specifically in the bakupdata function. SQL injection can threaten stored data, but the supplied sources do not provide severity, CVSS, authentication requirements, or a confirmed vendor fix.

Executive priority

Prioritize discovery first. If iCMS v7.0.16 is internet-facing or handles sensitive data, treat remediation as urgent because SQL injection can affect confidentiality and integrity. If the product is not present, no action is needed beyond documentation.

Technical view

The CVE record describes SQL injection in iCMS v7.0.16 through the bakupdata function. The source bundle does not define affected CPEs, CWE, required privileges, vulnerable parameter details, impact scope, or remediation version. Treat technical impact as unconfirmed beyond the reported SQL injection class.

Likely exposure

Likely limited to organizations running iCMS v7.0.16. Exposure depends on whether the bakupdata function is reachable, especially from public or less-trusted interfaces. Official affected-product metadata is incomplete in the supplied CVE data.

Exploitation context

The bundle includes a public GitHub Gist reference, but no KEV listing and no cited source confirming active exploitation. Do not assume exploitation in the wild from the provided evidence alone.

Researcher notes

Evidence is thin: the CVE description names iCMS v7.0.16 and bakupdata, but lacks CVSS, CWE, CPE, authentication context, impact details, and fix data. Validate against the referenced advisory material without relying on unverified exploit assumptions.

Mitigation direction

  • Inventory iCMS deployments and identify any v7.0.16 instances.
  • Check iCMS vendor or project guidance for a fixed release or workaround.
  • Restrict access to administrative and backup-data functions.
  • Apply least privilege to the application database account.
  • Review web and database logs for suspicious query-related errors.

Validation and detection

  • Confirm whether any internet-facing asset runs iCMS v7.0.16.
  • Verify bakupdata functionality is only accessible to authorized administrators.
  • Check vendor release notes for a patched version or advisory.
  • Review application logs for unusual database errors or request patterns.
  • Document compensating controls if no vendor fix is available.
Prepared
Confidence
medium
Sources
3

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

description · low confidence lookup

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 lookup
cve · low confidence lookup

CVE-2023-39806 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
3Timeline events
2ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.