LiveActive security incident?Get immediate response
CVE Record

CVE-2021-36431: 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_json_check() function in jocms/apps/mask/inc/mask.php.

CriticalCVSS 9.1Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2021-36431 is a critical SQL injection issue reported in jocms 0.8. A remote attacker could use the vulnerable code path to run SQL queries and access sensitive information. The source data does not identify a vendor fix or confirm real-world exploitation.

Executive priority

Treat this as high-priority for any confirmed jocms 0.8 deployment because it may expose sensitive data and allow database tampering. If jocms is not present, the immediate business risk is low, but asset inventory should confirm that conclusion.

Technical view

The CVE describes CWE-89 SQL injection in the jo_json_check() function in jocms/apps/mask/inc/mask.php. CVSS 3.1 is 9.1 with network access, low complexity, no privileges, and no user interaction. Confidentiality and integrity impact are high; availability impact is not rated.

Likely exposure

Exposure appears limited to organizations running jocms 0.8, especially if reachable over the internet. The CVE affected-product metadata is incomplete, so teams should verify deployments by application name, version, and referenced file path rather than relying only on CPE matching.

Exploitation context

The vulnerability is remotely reachable and unauthenticated according to the CVSS vector, which raises urgency. The source bundle does not show CISA KEV listing or other evidence of active exploitation, so active exploitation should not be assumed.

Researcher notes

The public record is sparse: it names jocms 0.8, a vulnerable function, and a GitHub issue, but affected vendor metadata is n/a and no patch is named in the provided bundle. Avoid overstating exploitation or fix availability.

Mitigation direction

  • Identify any jocms 0.8 deployments across internet-facing and internal assets.
  • Check the project issue and CVE sources for vendor guidance or fixes.
  • Restrict external access to affected jocms instances until remediation is confirmed.
  • Disable or isolate the affected component if business operations allow.
  • Increase monitoring for suspicious database errors or unusual requests to the referenced path.

Validation and detection

  • Confirm whether any deployed application is jocms 0.8.
  • Review deployed code for jo_json_check() in jocms/apps/mask/inc/mask.php.
  • Check web logs for unusual access to the referenced mask.php path.
  • Verify database logs for unexpected query patterns from the web application.
  • Document whether the instance is public, authenticated, or internally restricted.
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-36431 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-36431Attack 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.