CVE-2020-37012
Remote Code Execution in Tea LaTex 1.0 via /api.php Endpoint
Publication date: 2026-01-29
Last updated on: 2026-01-29
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| unknown_vendor | tea_latex | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-78 | The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in Tea LaTex 1.0 is a remote code execution flaw that allows unauthenticated attackers to execute arbitrary shell commands on the server. Attackers exploit the /api.php endpoint, specifically the tex2png API action, by submitting malicious LaTeX payloads that include shell commands. The vulnerability abuses the LaTeX \input command with a pipe to inject and execute system commands, enabling attackers to run arbitrary code remotely without authentication. [2]
How can this vulnerability impact me? :
This vulnerability can have severe impacts as it allows attackers to execute arbitrary commands on the server hosting Tea LaTex 1.0 without any authentication. This can lead to full system compromise, data theft, service disruption, installation of malware, or use of the server as a pivot point for further attacks. The exploit can open a reverse shell to the attacker, giving them remote control over the affected system. [2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring for suspicious POST requests to the /api.php endpoint with the action=tex2png parameter containing LaTeX payloads that include shell command injection patterns, such as the use of \input with pipe (|) characters. For example, you can use network monitoring tools or web server logs to search for requests containing patterns like '\input{|'. Additionally, you can use commands like: 1) grep -r '\\input{|}' /var/log/apache2/access.log 2) tcpdump or Wireshark filters to capture HTTP POST requests to /api.php?action=tex2png with suspicious payloads. 3) Use curl or similar tools to test the endpoint with crafted payloads to verify if the vulnerability exists. Example grep command: grep -r '\\input{|}' /path/to/webserver/logs [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the /api.php endpoint, especially the tex2png action, by implementing authentication and input validation to prevent malicious LaTeX payloads. Disable or sandbox the LaTeX processing functionality to prevent execution of shell commands. If possible, apply patches or updates from the vendor or remove the vulnerable Tea LaTex 1.0 application until a fix is available. Additionally, monitor network traffic for suspicious activity and block outgoing connections that could be used for reverse shells. [2]