LiveActive security incident?Get immediate response
CVE Record

CVE-2021-33925: SQL Injection vulnerability in nitinparashar30 cms-corephp through commit bdabe52ef282846823bda102728a35506...

SQL Injection vulnerability in nitinparashar30 cms-corephp through commit bdabe52ef282846823bda102728a35506d0ec8f9 (May 19, 2021) allows unauthenticated attackers to gain escilated privledges via a crafted login.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This is a critical SQL injection issue in the cms-corephp project. The CVE says an unauthenticated attacker could use a crafted login to gain elevated privileges, potentially affecting confidentiality, integrity, and availability. The source bundle does not identify packaged product versions or a confirmed fix.

Executive priority

Treat as urgent for any confirmed cms-corephp deployment because unauthenticated SQL injection can lead to account compromise and data exposure. Priority is lower only if asset review confirms the project is not used.

Technical view

CVE-2021-33925 is listed as CWE-89 SQL injection in nitinp1232/nitinparashar30 cms-corephp through commit bdabe52ef282846823bda102728a35506d0ec8f9. It has CVSS 3.1 score 9.8, network attack vector, low complexity, no privileges, and no user interaction.

Likely exposure

Exposure is likely limited to organizations running this specific cms-corephp codebase, especially deployments with the affected login functionality reachable over the network. The CVE metadata lists affected vendor, product, versions, and CPEs as n/a, so inventory must be code- and repository-based.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Public disclosure is referenced through a GitHub issue, but the bundle does not establish exploit use in the wild or provide patch status.

Researcher notes

Evidence is sparse: one CVE record, CVE List data, and a GitHub issue. Do not generalize this to unrelated CMS products. Focus validation on repository lineage, affected login code, exposure, and whether a local or upstream fix exists.

Mitigation direction

  • Inventory deployments derived from nitinp1232 cms-corephp.
  • Check the project repository and issue for maintainer guidance or fixed commits.
  • Restrict public access to affected login surfaces until remediated.
  • Use parameterized queries if maintaining an internal fork.
  • Monitor authentication and database logs for suspicious login activity.

Validation and detection

  • Confirm whether deployed code matches or predates the affected commit.
  • Identify exposed login routes in internet-facing environments.
  • Review login database access for unsafe SQL construction.
  • Check whether any local fork has already remediated the query handling.
  • Document uncertainty where product/version mapping is unavailable.
Prepared
Confidence
medium
Sources
3

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-2021-33925 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
2Source 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-2021-33925Attack 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.

CWE-89 · source CWE mapping

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.