LiveActive security incident?Get immediate response
CVE Record

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

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-36432 is a SQL injection flaw reported in jocms 0.8. A remote attacker could use the vulnerable mask function to run database queries and view sensitive information. The record does not provide complete vendor/product metadata or a named patch.

Executive priority

Treat this as a high-priority exposure if jocms 0.8 is present, especially on public web systems. The main business risk is unauthorized access to sensitive database information. If jocms is not used, document non-exposure.

Technical view

The CVE describes CWE-89 in jo_set_mask() within jocms/apps/mask/mask.php. CVSS 3.1 is 7.5, network-accessible, low complexity, no privileges, no user interaction, with high confidentiality impact and no listed integrity or availability impact.

Likely exposure

Exposure is most likely on internet-facing or reachable jocms 0.8 deployments where the mask application code is accessible. The affected CPE/vendor fields are listed as n/a, so asset confirmation must rely on application inventory and source path checks.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. A public GitHub issue is referenced, so technical details may be publicly available, but exploitation in the wild is not established by the supplied sources.

Researcher notes

Evidence is limited to the CVE description, CVSS vector, CWE-89 classification, and a GitHub issue reference. The CVSS vector emphasizes confidentiality impact, while the description says arbitrary SQL commands. No patch version, CPE, or exploitation telemetry is provided.

Mitigation direction

  • Inventory systems for jocms 0.8 and the affected mask.php path.
  • Check the project issue and vendor repository for confirmed fixes or upgrade guidance.
  • Restrict public access to affected jocms functionality until remediation is verified.
  • Apply available vendor fixes or upgrade guidance after testing.
  • Review database and web logs for suspicious access to the affected path.

Validation and detection

  • Confirm whether any deployed application is jocms 0.8.
  • Check whether jocms/apps/mask/mask.php is present and reachable.
  • Review logs for unexpected requests involving mask.php or mask functionality.
  • Run authorized vulnerability scanning for SQL injection without using destructive checks.
  • Verify remediation by retesting the affected route in a controlled environment.
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-36432 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
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2021-36432Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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.