Akaunting 3.1.8 special elements used in a template engine

Summaryinfo

A vulnerability was found in Akaunting 3.1.8. It has been classified as problematic. The impacted element is an unknown function. Performing a manipulation results in improper neutralization of special elements used in a template engine. This vulnerability is identified as CVE-2024-58293. The attack can be initiated remotely. Additionally, an exploit exists.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Akaunting 3.1.8. This affects an unknown code block. The manipulation with an unknown input leads to a improper neutralization of special elements used in a template engine vulnerability. CWE is classifying the issue as CWE-1336. The product uses a template engine to insert or process externally-influenced input, but it does not neutralize or incorrectly neutralizes special elements or syntax that can be interpreted as template expressions or other code directives when processed by the engine. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Akaunting 3.1.8 contains a server-side template injection vulnerability that allows authenticated administrators to execute template expressions in multiple form input fields. Attackers can inject template payloads in items, taxes, transactions, and vendor name fields to perform arithmetic operations and string manipulations.

The weakness was released by tmrswrr as 52030. It is possible to read the advisory at exploit-db.com. This vulnerability is uniquely identified as CVE-2024-58293 since 12/11/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. The exploitation needs additional levels of successful authentication. Technical details are unknown but a public exploit is available. The attack technique deployed by this issue is T1221 according to MITRE ATT&CK.

The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept.

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 (52030). Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Name

• Akaunting

Version

• 3.1.8

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion