{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25066 exists.","fix":"No fix has been published for CVE-2019-25066 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-25066 is a medium-severity vulnerability in unspecified ajenti, published on 9 Jun 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-25066 and fix it if it is affected.\n\nWhat it is: CVE-2019-25066 is a medium-severity vulnerability in unspecified ajenti, published on 9 Jun 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25066 exists.\n\nAffected product: unspecified ajenti. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2019-25066/ (Markdown: https://insights.sbomify.com/CVE-2019-25066/index.md)","id":"CVE-2019-25066","markdown":"https://insights.sbomify.com/CVE-2019-25066/index.md","name":"CVE-2019-25066","record":{"aliases":["GHSA-p28j-xhp9-88wp"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Ajenti web panel","requires_auth":"low_privilege","summary":"Remote attackers can exploit an API flaw in Ajenti to escalate privileges, requiring an upgrade to the latest version.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"ajenti","vendor":"ajenti"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"},{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"A vulnerability has been found in ajenti 2.1.31 and classified as critical. This vulnerability affects unknown code of the component API. The manipulation leads to privilege escalation. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 2.1.32 is able to address this issue. The name of the patch is 7aa146b724e0e20cfee2c71ca78fafbf53a8767c. It is recommended to upgrade the affected component.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2019-10-14","github_poc":0,"max_poc_stars":null,"metasploit":1,"nuclei":0,"refs":[{"date":"2019-10-14","kind":"metasploit","ref":"exploit/unix/webapp/ajenti_auth_username_cmd_injection","stars":null,"title":"Ajenti auth username Command Injection"}],"tier":"weaponised"},"has_fix":false,"headline":"ajenti API privileges management","id":"CVE-2019-25066","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"Podman/Varlink API Privilege Escalation","id":"CVE-2019-25067"},"packages":[],"prev":{"headline":"OpenNetAdmin os command injection","id":"CVE-2019-25065"},"products":["ajenti"],"published":"2022-06-09","related":[{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2018-1000082","kev_date_added":null,"published":"2018-03-13"},{"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"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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)"},{"class":"attribution","licence":"BSD-3-Clause","name":"Metasploit"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-15","vendors":["unspecified"]},"summary":"Remote attackers can exploit an API flaw in Ajenti to escalate privileges, requiring an upgrade to the latest version.","url":"https://insights.sbomify.com/CVE-2019-25066/"}