Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-85274 Overview
InvoicePlane, a self-hosted open source application for managing invoices, clients, and payments, contains a Cross-Site Request Forgery (CSRF) vulnerability [CWE-352] in versions prior to 1.7.2. The application exposes Recurring::stop() as a state-changing GET route without CSRF token validation. When an authenticated administrator loads attacker-controlled content that requests /invoices/recurring/stop/{id}, the application stops the selected recurring invoice. An attacker can target multiple identifiers to interrupt recurring billing and cause financial loss. The issue is fixed in version 1.7.2.
Critical Impact
Attackers can halt recurring billing workflows by tricking authenticated administrators into loading malicious content, disrupting revenue collection without needing credentials.
Affected Products
- InvoicePlane versions prior to 1.7.2
- Self-hosted InvoicePlane deployments exposing the recurring invoice module
- Administrator-facing instances accessible via browser sessions
Discovery Timeline
- 2026-09-25 - CVE-2026-85274 published to NVD
- 2026-09-28 - Last updated in NVD database
Technical Details for CVE-2026-85274
Vulnerability Analysis
The vulnerability resides in the Recurring controller within the InvoicePlane invoice module. The stop() method performs a state-changing operation that cancels a recurring invoice. Because the endpoint is reachable via a plain HTTP GET request and lacks CSRF token validation, any authenticated administrator session can be abused by an off-site attacker.
An attacker crafts a page containing an image tag, iframe, or script that triggers requests to /invoices/recurring/stop/{id} for one or many identifiers. When an authenticated admin visits that page, the browser automatically attaches the session cookie, and the application stops the targeted recurring invoices. The result is interrupted billing cycles and potential financial loss.
Root Cause
Two design flaws combine to produce the vulnerability. First, the stop() action is registered as a GET route rather than a POST route, violating safe-method semantics. Second, the controller performs no CSRF token verification before mutating application state. The patched template now wraps the stop action in a POST form with a CSRF token field, and the controller rejects requests failing ensure_valid_post_request().
Attack Vector
Exploitation requires an authenticated administrator to load attacker-controlled HTML, such as a phishing email link, a malicious website, or a compromised third-party page. No user credentials are needed, and no interaction beyond page load is required for the forged request to succeed. Multiple recurring invoice IDs can be targeted in a single page to maximize damage.
// Patched controller: application/modules/invoices/controllers/Recurring.php
public function stop($invoice_recurring_id)
{
if ( ! $this->ensure_valid_post_request('invoices/recurring/index')) {
return;
}
$this->mdl_invoices_recurring->stop($invoice_recurring_id);
redirect('invoices/recurring/index');
}
Source: InvoicePlane commit 2c76ef5
Detection Methods for CVE-2026-85274
Indicators of Compromise
- HTTP GET requests to /invoices/recurring/stop/{id} originating from cross-site Referer headers or unexpected external domains
- Unexplained state transitions of recurring invoices from active to stopped status in the InvoicePlane database
- Multiple sequential stop requests targeting different invoice_recurring_id values from a single administrator session
Detection Strategies
- Review web server access logs for GET requests to the invoices/recurring/stop/ path and correlate with administrator session activity
- Audit the InvoicePlane database ip_invoices_recurring table for recurring invoices that transitioned to a stopped state outside expected business workflows
- Inspect Referer and Origin headers on recurring invoice endpoints to identify requests not originating from the application itself
Monitoring Recommendations
- Enable application-level audit logging for all recurring invoice state changes with user, source IP, and timestamp
- Alert on bulk stop operations against recurring invoices within short time windows
- Monitor administrator browser sessions and investigate anomalous request patterns to invoice management endpoints
How to Mitigate CVE-2026-85274
Immediate Actions Required
- Upgrade InvoicePlane to version 1.7.2 or later, which enforces POST and CSRF token validation on the Recurring::stop() endpoint
- Audit recurring invoice records for unexpected stopped entries and restore legitimate billing cycles
- Instruct administrators to log out of InvoicePlane sessions when not actively using the application
Patch Information
The fix is included in InvoicePlane v1.7.2 and merged via Pull Request #1636. The patch converts the stop action from a GET link into a POST form with a CSRF token and adds ensure_valid_post_request() enforcement in the controller. Full details are documented in GitHub Security Advisory GHSA-qf9q-2hxm-4wh9.
Workarounds
- Restrict access to the InvoicePlane administrative interface to trusted IP ranges via web server or firewall rules
- Apply the controller and view changes from the upstream commit as a manual hotfix if an immediate upgrade is not feasible
- Require administrators to use isolated browser profiles when accessing InvoicePlane to limit cross-site session reuse
# Upgrade InvoicePlane to patched version
cd /var/www/invoiceplane
wget https://github.com/InvoicePlane/InvoicePlane/releases/download/v1.7.2/v1.7.2.zip
unzip v1.7.2.zip
# Follow the official upgrade guide to migrate configuration and database
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

