Skip to content
Fencer Vulns
high 7.1

CVE-2026-94455 json

Unauthenticated /enterprise/create-user mints lifetime top-tier organizations and discloses their API key

published 2026-09-22 47 d ago modified 2026-09-22 47 d ago also EUVD-2026-84547

cvss
7.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 18%
public exploits
0
none known

Summary

An HTTP endpoint intended for provisioning enterprise and reseller organisations is reachable without any session. The authentication middleware is bound only to an explicit list of controllers, and the enterprise controller is not on that list, so no authentication runs for these routes.

The endpoint's only check is that the request body carries a token bearing a valid signature from the instance secret. It does not check what that token was issued for. Login tokens are signed with the same secret and carry no purpose, audience or expiry claim, so an ordinary user's own session token satisfies the check.

Presented with such a token, the endpoint creates a new organisation holding the highest subscription tier, flagged as lifetime and with a channel allowance far above any sold plan, creates an organisation-owner account alongside it, and returns the new organisation's API key in the response body. That key is immediately valid against the public API.

Patch / fix

  • GitroomHQ postiz-app 2.4.0

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
47 d ago

Exploit prediction

0.26% chance of exploitation in the next 30 days, higher than 18% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L

Affected products

  • GitroomHQ postiz-app

Classification

Weakness
  • CWE-306 Missing Authentication for Critical Functionality
  • CWE-1390 Weak Authentication
  • CWE-345 Insufficient Verification of Data Authenticity
  • CWE-770 Allocation of Resources Without Limits or Throttling

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.