Home
» GitHub Advisories
» GHSA-677j-gfv9-ppcc
Description
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.
Basic information
Type
unreviewed
Severity
medium Advisory on GitHub
Open advisory ↗ Repository advisory
—
Source code
Not specified Published (advisory)
2026-07-07 00:30:59 UTC
Updated
2026-07-09 18:32:35 UTC
NVD published
2026-07-06
EPSS Score
Score
Percentile
0.16%
5.50%
CVSS Scores
Base score
Version
Severity
Vector
5.4
3.1
—
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
CWEs
CWE id
Name
CWE-1021
Improper Restriction of Rendered UI Layers or Frames
cvelogic
Threat Intelligence