CVE-2026-33543
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. Versions 0.7.2 and prior expose a guest API endpoint, /api/guest/staff/create, intended for initial administrator bootstrap. Due to a flawed admin-existence check, the endpoint remains usable after an administrator already exists. The flawed guard check uses is_countable() on a value that returns a Model_Admin object or null rather than a countable type, causing the expression to always evaluate as true and bypass the intended protection. As a result, an attacker can reach the unprotected endpoint to create a new administrator account and immediately authenticate, gaining a fully privileged admin session even when an admin already exists. This issue has been fixed in version 0.8.0.
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 confidenceFOSSBilling versions 0.7.2 and prior expose a guest API endpoint (/api/guest/staff/create) intended only for initial administrator setup. A flawed guard check uses is_countable() on a Model_Admin object or null return value, which always evaluates as true since these are not countable types. This allows unauthenticated attackers to create administrator accounts and obtain full admin privileges even when an administrator already exists.
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:H/VI:H/VA:H/SC:N/SI:N/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.
-
Locate FOSSBilling installationSearch for FOSSBilling directories on the web server, typically found in the web root. Look for the presence of index.php, composer.json, or src/ folder containing FOSSBilling code.Affected if FOSSBilling software is present on the system
-
Identify installed FOSSBilling versionCheck for a version file in the FOSSBilling root directory, or inspect composer.json for the version declaration. The version may also be displayed in the admin panel footer or in a VERSION file.Affected if The installed version is 0.7.2 or any earlier version (0.x.y where x < 7, or x = 7 and y <= 2)
-
Verify the vulnerable endpoint existsConfirm the file api/guest/staff/create.php (or equivalent routing to the staff/create endpoint) exists in the FOSSBilling installation under the api/guest/ directory.Affected if The /api/guest/staff/create endpoint file is present in the installation
-
Check admin account statusQuery the database or admin panel to determine if at least one administrator account already exists in the system. The vulnerability allows account creation even when admins exist due to the is_countable() flaw.Affected if An administrator account already exists in the system and the vulnerable endpoint is still accessible to unauthenticated users
A FOSSBilling installation is affected if it runs version 0.7.2 or prior and the /api/guest/staff/create endpoint remains accessible to unauthenticated users, allowing unauthorized admin account creation regardless of whether an admin already 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 version 0.8.0 or later which contains the corrected guard logic. If immediate upgrade is not feasible, restrict access to the /api/guest/ API endpoint at the web server or firewall level.
FOSSBilling version 0.8.0
- 1. Backup the existing FOSSBilling installation and database before proceeding with any changes.
- 2. Download FOSSBilling version 0.8.0 from the official GitHub repository (github.com/FOSSBilling/FOSSBilling).
- 3. Replace all existing FOSSBilling files with the new version 0.8.0 files, preserving any custom configuration files if required.
- 4. Verify that the /api/guest/staff/create endpoint is no longer accessible when an administrator account already exists in the system.
- 5. Test that existing administrator accounts can still authenticate normally.
- 6. Confirm the fix by reviewing the patched code: the flawed is_countable() check should be replaced with a proper null/empty check on the Model_Admin object.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-33543 — 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-33543 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