CVE WatchJul 8, 2026

CVE-2026-43918

FOSSBilling is a free, open-source billing and client management system. Prior to version 0.8.0, when a client or staff/admin account is sus

CVSS

—

No CVSS

EPSS

0.2%

p14

KEV

—

Exploit Today

0-100

Published: Jul 6, 2026 · Last modified: Jul 8, 2026 · CWE-613

EPSS · 30d

0.2%EPSS · 30 days0.2%

2026-07-072026-07-18

Technical description

FOSSBilling is a free, open-source billing and client management system. Prior to version 0.8.0, when a client or staff/admin account is suspended or marked inactive, existing authenticated sessions are not invalidated. The session identity loaders in src/di.php (loggedin_client and loggedin_admin) only reject sessions if the backing account record no longer exists in the database. They do not verify that the account's status is still active. This allows a suspended or deactivated user to retain full access until their session naturally expires. This issue has been fixed in version 0.8.0.

Official references

Related CVEs

CVECVSSEPSSKEVRExploitTitleMod.

CVE-2022-255906.5 MED

66.8%

——20SurveyKing v0.2.0 was discovered to retain users' session cookies after logout, allowing attackers to login to the system and access data using the browser cache when the user exits the application.10d CVE-2022-361799.8 CRI

56.7%

——17Fusiondirectory 1.3 suffers from Improper Session Handling.10d CVE-2022-415425.4 MED

45.4%

——14devhub 0.102.0 was discovered to contain a broken session control.10d CVE-2026-443837.5 HIG

43.1%

——13Multiple connections to the backend using the same charging station ID are allowed, which could allow an attacker to deploy multiple instances of malicious OCPP clients to overwhelm the backend.5d CVE-2022-346245.9 MED

40.4%

——12Mealie1.0.0beta3 does not terminate download tokens after a user logs out, allowing attackers to perform a man-in-the-middle attack via a crafted GET request.10d CVE-2026-492298.3 HIG

35.7%

——11Actual is a local-first personal finance app. Prior to 26.6.0, in OpenID multi-user mode, disabling a user only blocks future OpenID login for that identity, while existing Actual session tokens for the disabled user remain valid. The shared session validation path accepts any existing token row that has not expired without checking whether the associated user is still enabled, allowing a disabled user to continue calling authenticated server endpoints. This issue is fixed in version 26.6.0.9d