# CVE-2026-43643: Softaculous Virtualizor Authorization Bypass via Billing Module Handler

> Unauthenticated attackers can modify tenant account balances via the billing module, potentially causing service suspension.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Sep 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-g658-6cgx-fx2p

## What is CVE-2026-43643?

CVE-2026-43643 is a high-severity missing authorization vulnerability in Softaculous Virtualizor, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Softaculous Virtualizor before 3.2.9 (Patch 9) and 3.0.0 contains an authorization bypass vulnerability in the billing module handler that allows unauthenticated remote attackers to modify any tenant's account balance by supplying crafted act and from_billing_module parameters to the admin panel dispatcher. Attackers can send a POST request with arbitrary uid and balance values in the billing_data field to trigger an unauthenticated parameterized UPDATE against the users table, enabling account balance manipulation and potential automated service suspension for targeted accounts.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-43643?


## How do I fix CVE-2026-43643?

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

## Is CVE-2026-43643 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-43643 and fix it if it is affected.

What it is: CVE-2026-43643 is a high-severity missing authorization vulnerability in Softaculous Virtualizor, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-43643 in the wild and no public exploit code.

Affected product: Softaculous Virtualizor. 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-2026-43643/ (Markdown: https://insights.sbomify.com/CVE-2026-43643/index.md)
```

## Sources

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

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