CVE-2018-1000082 json
Ajenti version version 2 contains a Cross ite Request Forgery (CSRF) vulnerability in the command execution panel of the tool used to manag…
published 8y ago modified 4mo ago also PYSEC-2018-111 , EUVD-2018-0005
- cvss
- 8.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 70%
- public exploits
- 0
- none known
Summary
Ajenti version version 2 contains a Cross ite Request Forgery (CSRF) vulnerability in the command execution panel of the tool used to manage the server. that can result in Code execution on the server . This attack appear to be exploitable via Being a CSRF, victim interaction is needed, when the victim access the infected trigger of the CSRF any code that match the victim privledges on the server can be executed..
Is CVE-2018-1000082 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.28% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- medium.com https://medium.com/stolabs/security-issues-on-ajenti-d2b7526eaeee referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | ajenti-panel | all versions |
no fix listed |
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
medium.com
/stolabs/security-issues-on-ajenti-d2b7526eaeee
exploit, third-party-advisory, web
-
pypi.org
/project/ajenti-panel
package
-
nvd.nist.gov
/vuln/detail/CVE-2018-1000082
advisory
Sources
- CVE List CVE-2018-1000082
- NVD CVE-2018-1000082
- OSV PYSEC-2018-111
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.