LiveActive security incident?Get immediate response
CVE Record

CVE-2020-23966: SQL Injection vulnerability in victor cms 1.0 allows attackers to execute arbitrary commands via the post p...

SQL Injection vulnerability in victor cms 1.0 allows attackers to execute arbitrary commands via the post parameter to /post.php in a crafted GET request.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2020-23966 is a critical SQL injection flaw reported in Victor CMS 1.0. An unauthenticated attacker could abuse crafted web requests to affect confidentiality, integrity, and availability. Treat any internet-facing deployment as urgent until proven absent or remediated.

Executive priority

Prioritize as critical if Victor CMS is present, especially on public websites. The business risk is full compromise of site data or service availability. If the product is absent, document the negative finding and monitor for derivative code exposure.

Technical view

The CVE describes SQL injection in the post parameter of /post.php in Victor CMS 1.0, reachable by crafted GET request. CVSS 3.1 is 9.8 with network attack vector, low complexity, no privileges, no user interaction, and high impact across confidentiality, integrity, and availability.

Likely exposure

Exposure appears limited to systems running Victor CMS 1.0 or code derived from the referenced CMSsite project. The CVE affected-product metadata is incomplete, so teams should verify by software inventory and code provenance rather than relying on CPE matching.

Exploitation context

The source bundle does not show CISA KEV listing or other cited evidence of active exploitation. Public issue and repository references exist, so defenders should assume enough detail may be available for opportunistic testing, while avoiding unsupported claims of exploitation in the wild.

Researcher notes

Evidence is concise and partly incomplete: the CVE description names Victor CMS 1.0 and /post.php, but affected vendor/product fields are n/a. No patch, KEV status, or exploitation confirmation is provided in the bundle. Validation should focus on inventory, code review, and vendor issue tracking.

Mitigation direction

  • Identify and prioritize any Victor CMS 1.0 deployments.
  • Check the vendor repository and issue for fix guidance or patched code.
  • Remove or restrict internet access until remediation is confirmed.
  • Use parameterized queries for SQL access in any maintained fork.
  • Monitor /post.php requests and database error patterns.

Validation and detection

  • Inventory web assets for Victor CMS 1.0 or CMSsite-derived code.
  • Review /post.php handling of the post parameter.
  • Confirm whether local code uses parameterized SQL for this path.
  • Check logs for suspicious /post.php activity and database errors.
  • Verify any applied vendor or local fix through regression testing.
Prepared
Confidence
medium
Sources
4

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.

cwe · medium confidence lookup

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 lookup
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-2020-23966 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
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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.

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

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2020-23966Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

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