ajenti up to 2.2.13 HTTP Response Path ajenti-core/aj/http.py start_response clickjacking

Summaryinfo

A vulnerability labeled as problematic has been found in ajenti up to 2.2.13. This affects the function start_response of the file ajenti-core/aj/http.py of the component HTTP Response Path. The manipulation results in clickjacking. This vulnerability is cataloged as CVE-2026-38979. The attack may be launched remotely. There is no exploit available.

Detailsinfo

A vulnerability, which was classified as problematic, was found in ajenti up to 2.2.13. Affected is the function start_response of the file ajenti-core/aj/http.py of the component HTTP Response Path. The manipulation with an unknown input leads to a clickjacking vulnerability. CWE is classifying the issue as CWE-451. The user interface (UI) does not properly represent critical information to the user, allowing the information - or its source - to be obscured or spoofed. This is often a component in phishing attacks. This is going to have an impact on integrity. CVE summarizes:

ajenti through v2.2.13 has a clickjacking weakness in the browser-facing login and administrative UI. In ajenti-core/aj/http.py, the core HTTP response path initializes an empty header list, forwards handler-added headers verbatim, and finalizes responses through WSGI start_response() without adding anti-framing protections such as X-Frame-Options or a Content-Security-Policy frame-ancestors restriction.

The advisory is available at github.com. This vulnerability is traded as CVE-2026-38979 since 04/06/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Successful exploitation requires user interaction by the victim. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 07/07/2026). This vulnerability is assigned to T1566.003 by the MITRE ATT&CK project.

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

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Name

• ajenti

Version

• 2.2.0
• 2.2.1
• 2.2.2
• 2.2.3
• 2.2.4
• 2.2.5
• 2.2.6
• 2.2.7
• 2.2.8
• 2.2.9
• 2.2.10
• 2.2.11
• 2.2.12
• 2.2.13

Website

• Product: https://github.com/ajenti/ajenti/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion