CVE-2026-43643: Softaculous Virtualizor authorization bypass in billing module

CVE-2026-43643 · Severity: high · CVSS 7.5 · Published 2026-09-22

Softaculous Virtualizor, a virtual machine management platform, contains an authorization bypass vulnerability that allows attackers without credentials to manipulate tenant account balances. An attacker can modify billing information to suspend service for any user or gain unauthorized financial control, potentially disrupting hosted services or causing financial fraud.

Technologies: Softaculous Virtualizor. Vendors: Softaculous.

Quick answers

Is CVE-2026-43643 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-43643 being exploited in the wild.
How severe is CVE-2026-43643?
High severity, with a CVSS score of 7.5, published 22 September 2026.
Which products and versions are affected?
Softaculous Virtualizor before 3.2.9 (Patch 9), including 3.0.0.
Is there a fix for CVE-2026-43643?
A patch was published on 2026-09-01: Fix included in Virtualizor 3.2.9 (Patch 9) Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-43643 attacked?
It is in a hosted service.
Am I affected by CVE-2026-43643?
Check whether you run Softaculous Virtualizor at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability exists in the admin panel dispatcher's billing module handler, which fails to verify authentication before processing billing requests. An unauthenticated attacker can send a POST request with crafted act and from_billing_module parameters containing arbitrary uid and balance values, triggering an unvalidated SQL UPDATE against the users table. The issue affects Virtualizor before version 3.2.9 (Patch 9) and 3.0.0.

Affected products

  • Softaculous Virtualizor before 3.2.9 (Patch 9), including 3.0.0

Timeline

  • 2026-09-22: disclosed: CVE-2026-43643 published on NVD
  • 2026-09-01: patched: Fix included in Virtualizor 3.2.9 (Patch 9)

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.