# CVE-2022-34876: VICIDial 2.14b0.5 SVN 3550 was discovered to contain multiple SQL injection vulnerability at /vicidial/admin.php.

> Attackers can exploit SQL injection in the admin interface to read, modify, or destroy data and gain database administrator privileges.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jul 2022
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-vm9r-p8vp-v2fj

## What is CVE-2022-34876?

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.

### Official 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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2022-34876?

It affects 1 product.


Products: Vicidial Vicidial.

## How do I fix CVE-2022-34876?

No fix has been published for CVE-2022-34876 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-34876 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-34876 exists.

Public exploit code:

- VICIdial Multiple Authenticated SQLi (metasploit)

## Other vulnerabilities in VICIdial

- [CVE-2022-34879](https://insights.sbomify.com/CVE-2022-34879/): Cross-site scripting in VICIdial (medium 6.5)
- [CVE-2013-4468](https://insights.sbomify.com/CVE-2013-4468/): Command injection in n/a (medium 6.5)
- [CVE-2013-4467](https://insights.sbomify.com/CVE-2013-4467/): SQL injection in n/a (medium 6.5)
- [CVE-2022-34877](https://insights.sbomify.com/CVE-2022-34877/): SQL injection in VICIdial (medium 6.4)
- [CVE-2021-35377](https://insights.sbomify.com/CVE-2021-35377/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-34876 and fix it if it is affected.

What 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-34876 exists.

Affected product: VICIdial. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-34876/ (Markdown: https://insights.sbomify.com/CVE-2022-34876/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-34876
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-34876
- OSV: https://osv.dev/vulnerability/CVE-2022-34876

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-34876/
Summaries are generated and may contain mistakes; the official description above is the record.