CVE-2026-43925
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedFOSSBilling is a free, open-source billing and client management system. Prior to version 0.8.0, an unauthenticated mass assignment vulnerability in the client self-registration endpoint allows any visitor to assign themselves to an arbitrary client group during sign-up. Because client groups can gate promo code eligibility, an attacker may apply group-restricted discount codes and receive unauthorized discounts. Version 0.8.0 contains a patch. As a workaround, administrators can either remove group restrictions from promo codes or disable client self-registration (Settings → Clients → Disable signup).
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAn unauthenticated mass assignment vulnerability in FOSSBilling's client self-registration endpoint (prior to v0.8.0) allows any visitor to arbitrarily assign themselves to a client group during sign-up. Since client groups control promo code eligibility, attackers can exploit group-restricted discount codes to receive unauthorized discounts.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed FOSSBilling versionLocate the version information in the FOSSBilling installation - typically found in the admin panel under Settings > About or in a version file at the root of the installationAffected if The installed version is prior to v0.8.0 (any version from initial release up to but not including v0.8.0)
-
Verify client self-registration is enabledLog into the FOSSBilling admin panel and navigate to Settings > Clients, or inspect the configuration file that controls new client registration. Look for an option that allows visitors to register themselves as clients.Affected if Client self-registration is enabled AND the installed version is prior to v0.8.0
-
Examine promo codes for group restrictionsIn the admin panel, go to Promotions > Promo Codes and review each promo code. Check whether any promo code has a client group assignment setting that restricts eligibility to specific client groups.Affected if There exists at least one promo code with a client group restriction, self-registration is enabled, and the version is prior to v0.8.0
A user is affected if running FOSSBilling version prior to v0.8.0 with client self-registration enabled and at least one group-restricted promo code exists.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to FOSSBilling v0.8.0 or higher to apply the patch. Alternatively, as a workaround, remove group restrictions from promo codes or disable client self-registration in Settings → Clients.
FOSSBilling version 0.8.0
- 1. Back up your current FOSSBilling installation and database before upgrading
- 2. Download FOSSBilling version 0.8.0 from the official GitHub repository (github.com/FOSSBilling/FOSSBilling)
- 3. Follow the standard upgrade instructions for FOSSBilling (typically involves replacing core files while preserving configuration and customizations)
- 4. Verify the upgrade was successful by logging into the admin panel
- 5. Test the client registration endpoint to confirm the mass assignment vulnerability is patched
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-43925 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-43925 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data