Skip to main content

FOSSBilling CVE-2026-112374

| EUVDEUVD-2026-113897 MEDIUM
Cross-Site Request Forgery (CSRF) (CWE-352)
2026-10-30 VulnCheck GHSA-595p-xmhc-mfxv
5.1
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Attacker hosts auto-submitting staff login form
  2. Delivery
    Lure victim staff user to page
  3. Exploit
    Browser POSTs to staff_login without CSRF check
  4. Execution
    Victim browser bound to attacker's staff account
  5. Impact
    Capture victim's actions and entered data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V3 - Web Frontend Security Anti-CSRF tokens, SameSite cookies
MITRE ATT&CK

1 technique across 1 tactic: Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires a FOSSBilling instance running a version before 0.8.9 whose guest staff login endpoint (POST /api/guest/staff/login) handled by checkGuestClientAuthentication() lacks CSRF/Origin validation because only client_login and client_create are allowlisted. The attacker must possess valid staff-account credentials on that same instance (the form submits attacker-controlled credentials), and a victim staff user must visit the attacker-controlled page so their browser auto-submits the form (UI:P). Limiting factors: this is login CSRF, so impact is confined to forcing the victim's browser into the attacker's session (VI:L; no confidentiality or availability impact), and realizing harm depends on the victim subsequently entering sensitive data or performing actions within that attacker-controlled session; instances on 0.8.9 or later, or custom forms correctly sending the pre-login same-origin session token, are not exploitable.

Impact

This is a moderate-severity login CSRF (CWE-352), not a top-priority emergency. The input CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N) scores 5.1: network-reachable and low-complexity, but with only limited integrity impact (VI:L) and no confidentiality or availability impact, plus passive user interaction (UI:P) and PR:L. The signals are internally consistent and point to a bounded, lower-impact issue rather than a widespread exploitation threat: the Decision label is 'this_month' (not act_now/emergency), there is no CISA KEV listing, and no EPSS probability was supplied in the input, so widespread opportunistic exploitation cannot be quantified from the data provided. No confirmed public exploit code is listed - only vendor/VulnCheck advisories and the patch. The practical impact is session-fixation-style: a victim's browser is silently authenticated into the ATTACKER's staff account, meaning the attacker does not gain access to the victim's data but can trick the victim into operating within an account the attacker controls (phishing for data entry, capturing input). This is a real but lower-tier fix-this-cycle item.

Exploit ScenarioDerived

An attacker who holds their own staff account on a target FOSSBilling instance (before 0.8.9) hosts a malicious web page containing an auto-submitting HTML form that POSTs the attacker's own credentials to /api/guest/staff/login. When a victim staff user visits the page, because staff_login is not covered by checkGuestClientAuthentication()'s CSRF/Origin allowlist, their browser is silently logged into the attacker's staff account, after which actions or data the victim enters occur inside the attacker-controlled session. No confirmed public exploit code is listed in the input (advisory and patch references only).

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 30, 2026

Login cross-site request forgery in FOSSBilling before 0.8.9 lets a remote, low-privileged attacker silently authenticate a victim's browser into the attacker's own staff account by luring the victim to an auto-submitting HTML form that posts to the guest staff login endpoint (/api/guest/staff/login). The flaw exists because checkGuestClientAuthentication() only allowlisted client_login and client_create, so staff_login was processed without a CSRF token or Origin validation; the attacker must hold valid staff credentials on the target instance and the victim must load the attacker's page, which is why impact is limited to integrity of the victim's session rather than data disclosure. Affected deployments are FOSSBilling 0.1.0 through 0.8.8; the 0.8.9 release requires POST requests carrying a pre-login session token from a same-origin context. No public exploit code has been identified at time of analysis, EPSS and CISA KEV signals are absent, and the assessed risk is moderate rather than an emergency.

RemediationAI

Vendor-released patch: FOSSBilling 0.8.9 (released 2026-10-23), available from https://github.com/FOSSBilling/FOSSBilling/releases/tag/0.8.9 and described in advisory GHSA-h7w3-wp25-gf86; upgrading is the complete fix, and the release notes ask users to update as soon as possible because the release contains several security fixes. Plan for the documented breaking changes before rolling out: API errors that carry explicit HTTP status codes (400-599) now return that status instead of always 200, with codes 413, 436, 437 and 498 mapped to 400 while the original code is preserved in the JSON envelope, so integrations that assume 200 on error must be adjusted (#4266); guest authentication calls for client login, client signup and staff login must be POST requests carrying the pre-login session token from a same-origin context, so custom themes, embed forms and API integrations posting directly to these endpoints must be updated to send the token as the shipped forms do (#4474); guest cart mutations now also require a session-bound CSRF token and reject cross-origin browser requests, affecting custom storefronts (#4546); and gateway return, cancel and thank-you URLs now route through a dedicated /invoice/payment-return page with the legacy session restore_token flow removed, so custom gateway or theme code relying on that flow must migrate (#4474). Until the upgrade is in place, the exposure is narrowed by ensuring staff log into the staff area only through the vendor-shipped forms rather than third-party or embedded login pages, accepting that this does not close the endpoint-level gap; there is no documented standalone configuration toggle that adds CSRF or Origin validation to staff_login on pre-0.8.9 releases.

Affected VersionsENISA

FOSSBilling 0.1.0 <0.8.9

Affected Packages

euvd fossbilling fix: 0.8.9

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

CWE-352 (cross-site request forgery) in a PHP-based billing and client management application. FOSSBilling's guest API routes authentication calls through a guard function, checkGuestClientAuthentication(), which acts as an allowlist of endpoints considered safe to reach without an established session. Before 0.8.9 that allowlist covered only client_login and client_create, so requests to the staff guest login endpoint were handled without the CSRF token or same-origin checks applied elsewhere, making the state-changing login action forgeable from a third-party origin. The shipped fix ties guest authentication calls (client login, client signup, and staff login) to POST requests that must carry a pre-login session token issued in a same-origin context, and the release notes state the token is now embedded in the admin login, client login and signup, order-button and embed login forms. The CPE entry cpe:2.3:a:fossbilling:fossbilling:* with the EUVD range 0.1.0 through <0.8.9 indicates the whole release history prior to 0.8.9 is in scope. Because this is login CSRF, the forged request establishes a session bound to the attacker's account; the practical consequence depends on what the victim subsequently enters or does inside that session, and the assessed CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:R, C:N/I:L/A:N) reflects that limited integrity impact rather than direct compromise of the victim's own account.

Know when Fossbilling gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulnCheck) PRIMARY 5.1 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
vuln.today AI 3.5 LOW

Network-delivered CSRF with low complexity but requiring the attacker's own valid staff credentials (PR:L) and victim browsing (UI:R); login CSRF yields only limited integrity impact with no confidentiality or availability loss.

3.1 AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
Passive
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
Low
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

FOSSBilling before 0.8.9 contains a Cross-Site Request Forgery vulnerability in the staff guest login endpoint (POST /api/guest/staff/login) that allows remote attackers to force authentication because checkGuestClientAuthentication() only allowlists client_login and client_create, leaving staff_login without CSRF or Origin validation. Attackers can host an auto-submitting HTML form with attacker-controlled credentials to silently log a victim's browser into the attacker's staff account.

Threat Intelligence Overview

EPSS Score
0.2%
Top 93% exploitable
Prevalence
Low
open-source self-hosted billing software, modest niche deployment footprint
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact· derived
Medium

Priority Score

26
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Request Forgery exploits the automatic credential inclusion behavior of web browsers.

CVE-2026-27604 CRITICAL POC
10.0 Jun 23

Authorization bypass in FOSSBilling versions 0.5.4 through 0.7.x allows unauthenticated remote attackers to invoke privi

CVE-2023-3490 CRITICAL POC
9.8 Jun 30

SQL Injection in GitHub repository fossbilling/fossbilling prior to 0.5.3. Rated critical severity (CVSS 9.8), this vuln

CVE-2026-28496 CRITICAL POC
9.4 Jun 23

Server-side template injection in FOSSBilling versions prior to 0.8.0 allows authenticated administrators to execute arb

CVE-2023-3491 HIGH POC
8.8 Jun 30

Unrestricted Upload of File with Dangerous Type in GitHub repository fossbilling/fossbilling prior to 0.5.3. Rated high

CVE-2023-3230 HIGH POC
7.5 Jun 14

Missing Authorization in GitHub repository fossbilling/fossbilling prior to 0.5.0. Rated high severity (CVSS 7.5), this

CVE-2023-3393 HIGH POC
7.2 Jun 23

Code Injection in GitHub repository fossbilling/fossbilling prior to 0.5.1. Rated high severity (CVSS 7.2), this vulnera

CVE-2023-3229 MEDIUM POC
6.5 Jun 14

Business Logic Errors in GitHub repository fossbilling/fossbilling prior to 0.5.0. Rated medium severity (CVSS 6.5), thi

CVE-2023-3521 MEDIUM POC
6.1 Jul 06

Cross-site Scripting (XSS) - Reflected in GitHub repository fossbilling/fossbilling prior to 0.5.4. Rated medium severit

CVE-2023-4005 CRITICAL
9.8 Jul 31

Insufficient Session Expiration in GitHub repository fossbilling/fossbilling prior to 0.5.5. Rated critical severity (CV

CVE-2023-3228 MEDIUM POC
5.7 Jun 14

Business Logic Errors in GitHub repository fossbilling/fossbilling prior to 0.5.0. Rated medium severity (CVSS 5.7), thi

CVE-2023-3227 MEDIUM POC
5.7 Jun 14

Insufficient Granularity of Access Control in GitHub repository fossbilling/fossbilling prior to 0.5.0. Rated medium sev

CVE-2023-3394 MEDIUM POC
5.4 Jun 23

Session Fixation in GitHub repository fossbilling/fossbilling prior to 0.5.1. Rated medium severity (CVSS 5.4), this vul

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy