{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-34876 exists.","fix":"No fix has been published for CVE-2022-34876 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-34876 is a medium-severity SQL injection vulnerability in VICIdial, published on 5 Jul 2022. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-34876 and fix it if it is affected.\n\nWhat it is: CVE-2022-34876 is a medium-severity SQL injection vulnerability in VICIdial, published on 5 Jul 2022. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-34876 exists.\n\nAffected product: VICIdial. 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-2022-34876/ (Markdown: https://insights.sbomify.com/CVE-2022-34876/index.md)","id":"CVE-2022-34876","markdown":"https://insights.sbomify.com/CVE-2022-34876/index.md","name":"CVE-2022-34876","record":{"aliases":["GHSA-vm9r-p8vp-v2fj"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"VICIdial call center","requires_auth":"high_privilege","summary":"Attackers can exploit SQL injection in the admin interface to read, modify, or destroy data and gain database administrator privileges.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"rapid7","cpe":[{"product":"vicidial","vendor":"vicidial"}],"cvss":{"score":5.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"SQL Injection vulnerability in admin interface (/vicidial/admin.php) of VICIdial via modify_email_accounts, access_recordings, and agentcall_email parameters allows attacker to spoof identity, tamper with existing data, allow the complete disclosure of all data on the system, destroy the data or make it otherwise unavailable, and become administrators of the database server. This issue affects: VICIdial 2.14b0.5 versions prior to 3555.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2022-04-19","github_poc":0,"max_poc_stars":null,"metasploit":1,"nuclei":0,"refs":[{"date":"2022-04-19","kind":"metasploit","ref":"auxiliary/scanner/http/vicidial_multiple_sqli","stars":null,"title":"VICIdial Multiple Authenticated SQLi"}],"tier":"weaponised"},"has_fix":null,"headline":"VICIDial 2.14b0.5 SVN 3550 was discovered to contain multiple SQL injection vulnerability at /vicidial/admin.php.","id":"CVE-2022-34876","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"SQL injection in VICIdial","id":"CVE-2022-34877"},"packages":[],"prev":{"headline":"Information disclosure in PDF Reader","id":"CVE-2022-34875"},"products":["VICIdial"],"published":"2022-07-05","related":[{"cvss_score":6.5,"headline":"Cross-site scripting in VICIdial","id":"CVE-2022-34879","kev_date_added":null,"published":"2022-07-05"},{"cvss_score":6.5,"headline":"Command injection in n/a","id":"CVE-2013-4468","kev_date_added":null,"published":"2014-05-14"},{"cvss_score":6.5,"headline":"SQL injection in n/a","id":"CVE-2013-4467","kev_date_added":null,"published":"2014-03-11"},{"cvss_score":6.4,"headline":"SQL injection in VICIdial","id":"CVE-2022-34877","kev_date_added":null,"published":"2022-07-05"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2021-35377","kev_date_added":null,"published":"2023-03-06"},{"cvss_score":5.5,"headline":"VICIDial 2.14b0.5 SVN 3550 was discovered to contain a SQL injection vulnerability at /vicidial/user_stats.php.","id":"CVE-2022-34878","kev_date_added":null,"published":"2022-07-05"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["VICIdial"]},"summary":"Attackers can exploit SQL injection in the admin interface to read, modify, or destroy data and gain database administrator privileges.","url":"https://insights.sbomify.com/CVE-2022-34876/"}