{"answers":{"affected":"1 open source package ship an affected version, including ajenti-panel. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-1000082 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-1000082 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-1000082 is a high-severity vulnerability in n/a, published on 13 Mar 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2018-1000082 and fix it if it is affected.\n\nWhat it is: CVE-2018-1000082 is a high-severity vulnerability in n/a, published on 13 Mar 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2018-1000082 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- ajenti-panel (PyPI): affected all versions; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2018-1000082/ (Markdown: https://insights.sbomify.com/CVE-2018-1000082/index.md)","id":"CVE-2018-1000082","markdown":"https://insights.sbomify.com/CVE-2018-1000082/index.md","name":"CVE-2018-1000082","record":{"aliases":["GHSA-2w58-27j5-f99h","PYSEC-2018-111"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Ajenti server management","requires_auth":"none","summary":"A CSRF vulnerability in Ajenti allows attackers to execute arbitrary code on the server by tricking an authenticated user into visiting a malicious page.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ajenti","vendor":"ajenti"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"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..","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Cross-site request forgery in n/a","id":"CVE-2018-1000082","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"csrf","year":"2018"},"n_packages":1,"n_references":1,"next":{"headline":"Information disclosure in n/a","id":"CVE-2018-1000083"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":[],"package":"ajenti-panel","purl":"pkg:pypi/ajenti-panel","source":"PYSEC-2018-111"}],"prev":{"headline":"Denial of service in n/a","id":"CVE-2018-1000081"},"products":["n/a"],"published":"2018-03-13","related":[{"cvss_score":8.1,"headline":"Ajenti has a potential Remote Code Execution","id":"CVE-2026-27975","kev_date_added":null,"published":"2026-02-26"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2018-1000081","kev_date_added":null,"published":"2018-03-13"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2018-1000126","kev_date_added":null,"published":"2018-03-13"},{"cvss_score":7.2,"headline":"Ajenti has an authorization bypass during custom package installation","id":"CVE-2026-35175","kev_date_added":null,"published":"2026-04-06"},{"cvss_score":6.5,"headline":"Missing authorization in n/a","id":"CVE-2018-1000080","kev_date_added":null,"published":"2018-03-13"},{"cvss_score":6.3,"headline":"ajenti API privileges management","id":"CVE-2019-25066","kev_date_added":null,"published":"2022-06-09"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"A CSRF vulnerability in Ajenti allows attackers to execute arbitrary code on the server by tricking an authenticated user into visiting a malicious page.","url":"https://insights.sbomify.com/CVE-2018-1000082/"}