# CVE-2017-6513: Missing authorization in n/a

> Remote authenticated users can control other virtual machines by accessing a modified URL due to incorrect user verification in the reseller module.

- **Severity:** Critical 9.9 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-3g5f-h429-8r64

## What is CVE-2017-6513?

CVE-2017-6513 is a critical missing authorization vulnerability in n/a, published on 11 Mar 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The WHMCS Reseller Module V2 2.0.2 in Softaculous Virtualizor before 2.9.1.0 does not verify the user correctly, which allows remote authenticated users to control other virtual machines managed by Virtualizor by accessing a modified URL.

Weakness: CWE-275

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

It affects 1 product.


Products: Softaculous Whmcs Reseller Module.

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

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

## Is CVE-2017-6513 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-6513 is a critical missing authorization vulnerability in n/a, published on 11 Mar 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-6513 in the wild and no public exploit code.

Affected product: n/a. 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-2017-6513/ (Markdown: https://insights.sbomify.com/CVE-2017-6513/index.md)
```

## Sources

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

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