LiveActive security incident?Get immediate response
CVE Record

CVE-2021-36433: SQL injection vulnerability in jocms 0.8 allows remote attackers to run arbitrary SQL commands and view sen...

SQL injection vulnerability in jocms 0.8 allows remote attackers to run arbitrary SQL commands and view sentivie information via jo_delete_mask function in jocms/apps/mask/mask.php.

CriticalCVSS 9.1Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2021-36433 is a critical SQL injection issue reported in jocms 0.8. A remote attacker could run arbitrary database queries and view sensitive information through the jo_delete_mask function. The public record does not identify a vendor advisory, fixed version, or CPE data.

Executive priority

Prioritize this as urgent for any confirmed jocms 0.8 deployment handling sensitive data. The risk is data theft or unauthorized database modification, but business impact depends on whether the niche affected software is present and reachable.

Technical view

The CVE describes CWE-89 SQL injection in jocms/apps/mask/mask.php, specifically the jo_delete_mask function. CVSS 3.1 is 9.1: network reachable, low complexity, no privileges, no user interaction, with high confidentiality and integrity impact and no availability impact.

Likely exposure

Exposure is most likely where jocms 0.8 is deployed, especially if the affected mask functionality is reachable over a network. The CVE metadata lists no vendor, CPE, or product inventory identifiers, so asset discovery must rely on application knowledge and code review.

Exploitation context

The CVSS vector supports remote unauthenticated exploitability, but the source bundle does not show CISA KEV listing or confirmed active exploitation. Treat exploit status as unconfirmed. The available public evidence is the CVE record and a linked GitHub issue.

Researcher notes

Evidence is limited. The affected metadata fields are n/a, but the description names jocms 0.8 and the vulnerable file/function. No patch, workaround, exploit-in-the-wild confirmation, or KEV listing is provided in the supplied sources.

Mitigation direction

  • Identify and prioritize any jocms 0.8 deployments.
  • Check the upstream project issue for vendor guidance or a fixed release.
  • Remove or isolate affected jocms instances if no fix is available.
  • Restrict network access to the application while remediation is assessed.
  • Back up and review database integrity before returning service to normal.

Validation and detection

  • Confirm deployed jocms versions and reachable routes.
  • Inspect jocms/apps/mask/mask.php for jo_delete_mask usage.
  • Review application logs for suspicious mask deletion activity.
  • Review database logs for unexpected read or write queries.
  • Verify whether any upstream patch or advisory now exists.
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-36433 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.1 (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:N

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.1CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N3.95.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.1Critical
CVSS 3.1 vector shape for CVE-2021-36433Attack 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:N

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

Source materials

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.