AMSS++ 4.31 Mail maildetail.php ID sql injection

Summaryinfo

A vulnerability classified as critical has been found in AMSS++ 4.31. Affected is an unknown function of the file /modules/mail/main/maildetail.php of the component Mail Module. Performing a manipulation of the argument ID results in sql injection. This vulnerability is known as CVE-2020-37141. Remote exploitation of the attack is possible. Furthermore, an exploit is available.

Detailsinfo

A vulnerability was found in AMSS++ 4.31. It has been classified as critical. This affects some unknown processing of the file /modules/mail/main/maildetail.php of the component Mail Module. The manipulation of the argument id with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

AMSS++ version 4.31 contains a SQL injection vulnerability in the mail module's maildetail.php script through the 'id' parameter. Attackers can manipulate the 'id' parameter in /modules/mail/main/maildetail.php to inject malicious SQL queries and potentially access or modify database contents.

The weakness was published by indoushka as 48109. The advisory is shared at exploit-db.com. This vulnerability is uniquely identified as CVE-2020-37141 since 02/03/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details and a public exploit are known. MITRE ATT&CK project uses the attack technique T1505 for this issue.

The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:modules/mail/main/maildetail.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.

The vulnerability is also documented in the vulnerability database at Exploit-DB (48109). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• AMSS++

Version

• 4.31

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion