LiveActive security incident?Get immediate response
CVE Record

CVE-2020-37012: Tea LaTex 1.0 - Remote Code Execution

Tea LaTex 1.0 contains a remote code execution vulnerability that allows unauthenticated attackers to execute arbitrary shell commands through the /api.php endpoint. Attackers can craft a malicious LaTeX payload with shell commands that are executed when processed by the application's tex2png API action.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Tea LaTex 1.0 has a critical flaw that can let an unauthenticated attacker run operating-system commands on the server. If this service is exposed to the internet, compromise could lead to data theft, service disruption, or server takeover.

Executive priority

Treat as urgent for any exposed deployment. The flaw is unauthenticated, network-reachable, and rated CVSS 9.8, so vulnerable systems should be isolated or removed quickly while remediation guidance is confirmed.

Technical view

CVE-2020-37012 is a CWE-78 command injection issue in Tea LaTex 1.0. The reported vulnerable path is the /api.php endpoint, where the tex2png API action processes crafted LaTeX content in a way that can execute arbitrary shell commands.

Likely exposure

Highest exposure is any internet-facing Tea LaTex 1.0 instance, especially where /api.php is reachable. Internal deployments remain at risk if reachable by untrusted users or compromised hosts.

Exploitation context

A public ExploitDB reference is listed, indicating exploit information is publicly available. The provided sources do not show CISA KEV listing or confirmed active exploitation.

Researcher notes

Sources identify Tea LaTex 1.0 as affected and describe command execution through LaTeX processing in tex2png. Patch status is not provided in the source bundle, so avoid assuming a fixed version without checking vendor materials.

Mitigation direction

  • Identify and prioritize all Tea LaTex 1.0 deployments.
  • Restrict public access to /api.php and the application immediately.
  • Disable or remove Tea LaTex if not business-critical.
  • Check the project and advisory sources for vendor remediation guidance.
  • Place the service behind authentication, network controls, or isolation where removal is not possible.

Validation and detection

  • Confirm whether Tea LaTex 1.0 is installed or deployed.
  • Verify whether /api.php is reachable from untrusted networks.
  • Review application logs for unusual tex2png API activity.
  • Check host logs for unexpected process execution by the web service.
  • Document compensating controls and remaining exposure.
Prepared
Confidence
high
Sources
5

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-78: Command execution behavior lookup

Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. 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

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. 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-37012 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
4Source 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-37012Attack 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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ammarfaizi2Tea LaTex1.0Listed
Weakness

CWE details

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

CWE-78 · source CWE mapping

Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.