# CVE-2017-6086: ViMbAdmin CSRF Vulnerabilities

> Remote attackers can hijack administrator sessions to add, remove, or modify users, mailboxes, and aliases via crafted requests.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-rrmf-fpmm-jpwr

## What is CVE-2017-6086?

CVE-2017-6086 is a high-severity vulnerability in n/a, published on 27 Jun 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site request forgery (CSRF) vulnerabilities in the addAction and purgeAction functions in ViMbAdmin 3.0.15 allow remote attackers to hijack the authentication of logged administrators to (1) add an administrator user via a crafted POST request to <vimbadmin directory>/application/controllers/DomainController.php, (2) remove an administrator user via a crafted GET request to <vimbadmin directory>/application/controllers/DomainController.php, (3) change an administrator password via a crafted POST request to <vimbadmin directory>/application/controllers/DomainController.php, (4) add a mailbox via a crafted POST request to <vimbadmin directory>/application/controllers/MailboxController.php, (5) delete a mailbox via a crafted POST request to <vimbadmin directory>/application/controllers/MailboxController.php, (6) archive a mailbox address via a crafted GET request to <vimbadmin directory>/application/controllers/ArchiveController.php, (7) add an alias address via a crafted POST request to <vimbadmin directory>/application/controllers/AliasController.php, or (8) remove an alias address via a crafted GET request to <vimbadmin directory>/application/controllers/AliasController.php.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2017-6086?

2 open source packages ship an affected version, including opensolutions/vimbadmin. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `opensolutions/vimbadmin` | Packagist | All versions to 3.0.15 | None |
| `opensolutions/vimbadmin` | Packagist | All versions to 3.0.15 | None |

Products: Vimbadmin Vimbadmin.

## How do I fix CVE-2017-6086?

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

## Is CVE-2017-6086 being exploited?

There is no known exploitation of CVE-2017-6086 in the wild and no public exploit code.

Public exploit code:

- ViMbAdmin 3.0.15 - Multiple Cross-Site Request Forgery Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2017-5870](https://insights.sbomify.com/CVE-2017-5870/): ViMbAdmin Cross-site Scripting Vulnerabilities (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-6086 and fix it if it is affected.

What it is: CVE-2017-6086 is a high-severity vulnerability in n/a, published on 27 Jun 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-6086 in the wild and no public exploit code.

Affected packages and fixed versions:
- opensolutions/vimbadmin (Packagist): affected all versions up to 3.0.15; no fix listed
- opensolutions/vimbadmin (Packagist): affected all versions up to 3.0.15; no fix listed

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-2017-6086/ (Markdown: https://insights.sbomify.com/CVE-2017-6086/index.md)
```

## Sources

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

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