ammarfaizi2 Tea LaTex 1.0 LaTeX /api.php os command injection

Summaryinfo

A vulnerability was found in ammarfaizi2 Tea LaTex 1.0 and classified as critical. This impacts an unknown function of the file /api.php of the component LaTeX Handler. Executing a manipulation can lead to os command injection. This vulnerability is handled as CVE-2020-37012. The attack can be executed remotely. Additionally, an exploit exists.

Detailsinfo

A vulnerability classified as critical was found in ammarfaizi2 Tea LaTex 1.0. This vulnerability affects an unknown code of the file /api.php of the component LaTeX Handler. The manipulation with an unknown input leads to a os command injection vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

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.

The weakness was released by nepska as 48805. The advisory is shared for download at exploit-db.com. This vulnerability was named CVE-2020-37012 since 01/28/2026. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Technical details and also a public exploit are known. The MITRE ATT&CK project declares the attack technique as T1202.

It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:api.php it is possible to find vulnerable targets with Google Hacking.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

• ammarfaizi2

Name

• Tea LaTex

Version

• 1.0

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion