Skip to main content
Vulnerability Database/CVE-2026-85289

CVE-2026-85289: InvoicePlane CSRF Vulnerability

CVE-2026-85289 is a cross-site request forgery flaw in InvoicePlane that allows attackers to delete financial records through authenticated sessions. This post explains its impact, affected versions, and mitigation steps.

Published:

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-85289 Overview

CVE-2026-85289 is a Cross-Site Request Forgery (CSRF) vulnerability in InvoicePlane, a self-hosted open source application for managing invoices, clients, and payments. Versions prior to 1.7.2 omit the ensure_valid_post_request() call from several delete endpoints, including Payments::delete(), Recurring::delete(), and User_clients::delete(). The affected routes require POST but do not validate the CSRF token. An attacker can trick an authenticated administrator into submitting a cross-origin form that deletes financial records and other application data. The issue is tracked under [CWE-352] and resolved in version 1.7.2.

Critical Impact

An authenticated administrator visiting an attacker-controlled page can be coerced into deleting invoices, payments, recurring billing records, and user-client assignments without consent.

Affected Products

  • InvoicePlane versions prior to 1.7.2
  • Payments, Recurring, User_clients, Email_templates, and Families controllers
  • Self-hosted InvoicePlane deployments accessible to administrators via browser

Discovery Timeline

  • 2026-09-25 - CVE-2026-85289 published to NVD
  • 2026-09-28 - Last updated in NVD database

Technical Details for CVE-2026-85289

Vulnerability Analysis

InvoicePlane uses a helper named ensure_valid_post_request() to verify a CSRF token on state-changing POST requests. Several delete endpoints in the application failed to invoke this helper. Although the routes are declared as POST-only, PHP controllers that skip the token check will still execute the deletion when the request body is submitted from any origin. Browsers automatically attach the administrator's session cookie to the cross-origin POST, satisfying the authentication requirement.

Successful exploitation requires user interaction: an authenticated administrator must visit an attacker-controlled page that auto-submits a hidden form. The resulting request destroys records in the database through functions such as mdl_payments->delete() and mdl_families->delete(). Confidentiality and availability are unaffected directly, but integrity of financial data is compromised through unauthorized deletions.

Root Cause

The root cause is a missing CSRF token validation step in multiple controller delete actions. The project relies on ensure_valid_post_request() for anti-CSRF protection, and the omission in Payments::delete(), Recurring::delete(), User_clients::delete(), Email_templates::delete(), and Families::delete() leaves these endpoints trusting the browser's session cookie as sole authorization.

Attack Vector

An attacker hosts a page containing an auto-submitting form targeting a vulnerable endpoint, for example POST /index.php/payments/delete/<id>. When an authenticated InvoicePlane administrator visits the page, the browser sends the request with session cookies, and the server executes the deletion. No credentials or server-side access are required by the attacker.

php
// Patch adding CSRF validation to Email_templates::delete()
public function delete($id)
{
    if ( ! $this->ensure_valid_post_request('email_templates')) {
        return;
    }

    $this->mdl_email_templates->delete($id);
    redirect('email_templates');
}
// Source: https://github.com/InvoicePlane/InvoicePlane/commit/215b8c1acca7560d00b7e463fb1c6fe98235ab95
php
// Patch adding CSRF validation to Families::delete()
public function delete($id)
{
    if ( ! $this->ensure_valid_post_request('families')) {
        return;
    }

    $this->mdl_families->delete($id);
    redirect('families');
}
// Source: https://github.com/InvoicePlane/InvoicePlane/commit/215b8c1acca7560d00b7e463fb1c6fe98235ab95

Detection Methods for CVE-2026-85289

Indicators of Compromise

  • Unexplained deletions of payment, recurring billing, or client assignment records in InvoicePlane audit logs or database tables.
  • POST requests to /payments/delete/, /recurring/delete/, or /user_clients/delete/ endpoints with HTTP Referer or Origin headers pointing to external domains.
  • Administrator session activity immediately following navigation to unknown or suspicious external URLs in browser history.

Detection Strategies

  • Review web server access logs for POST requests to delete routes where the Referer header does not match the InvoicePlane host.
  • Correlate browser proxy telemetry with InvoicePlane delete actions to spot cross-origin submissions originating from unexpected pages.
  • Enable database-level audit logging on invoice, payment, and client tables to flag deletion bursts tied to a single admin session.

Monitoring Recommendations

  • Alert on any delete action in InvoicePlane performed outside normal administrator working hours.
  • Monitor outbound email and user client assignment tables for sudden row-count drops.
  • Track administrator browsing patterns using endpoint telemetry to identify sessions that visit untrusted sites immediately before data loss events.

How to Mitigate CVE-2026-85289

Immediate Actions Required

  • Upgrade all InvoicePlane instances to version 1.7.2 or later, which adds ensure_valid_post_request() to the affected delete endpoints.
  • Instruct administrators to log out of InvoicePlane when not actively using it and to avoid browsing untrusted sites in the same session.
  • Review recent deletion activity in payments, recurring, and user_clients tables and restore from backup if unauthorized changes are found.

Patch Information

The fix is included in InvoicePlane 1.7.2. See the GitHub Security Advisory GHSA-9372, the upstream commit 215b8c1, Pull Request #1637, and the v1.7.2 release notes.

Workarounds

  • Restrict access to the InvoicePlane administration interface using network controls, allowing only trusted source IPs.
  • Deploy a reverse proxy or web application firewall rule that blocks POST requests to InvoicePlane delete endpoints when Origin or Referer headers do not match the application's own hostname.
  • Require administrators to use a dedicated browser profile for InvoicePlane that is not used for general web browsing.
bash
# Example nginx snippet enforcing same-origin on delete endpoints
location ~ ^/index\.php/(payments|recurring|user_clients|email_templates|families)/delete/ {
    if ($http_origin !~* "^https://invoiceplane\.example\.com$") {
        return 403;
    }
    include fastcgi_params;
    fastcgi_pass php-fpm;
}

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

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.