Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure authenticated admin to attacker page
-
DeliveryBrowser auto-loads /invoices/recurring/stop/{id}
-
ExploitForged GET passes with no CSRF token
-
ExecutionRecurring invoices stopped
-
ImpactBilling interrupted, financial loss
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 | Exploitation requires a victim who is an authenticated InvoicePlane administrator with an active session to load attacker-controlled web content while that session is valid; the vulnerable endpoint is the state-changing GET route /invoices/recurring/stop/{id} in Recurring::stop() which, prior to 1.7.2, accepts requests without CSRF token validation. Limiting factors: only versions before 1.7.2 are affected; the target recurring-invoice IDs must be known or brute-forced; and the impact is confined to stopping recurring billing (no data disclosure or account compromise). No click is needed once the admin loads the page (auto-fetching <img>), but the admin-session precondition (UI:R) meaningfully constrains real-world exploitation. |
| Impact | This is a genuine but moderate-severity CSRF flaw (CWE-352) confirmed by the vendor advisory (GHSA-qf9q-2hxm-4wh9), the fixing PR #1636, commit 2c76ef56, and the v1.7.2 release. The NVD CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N, 6.5) is internally consistent: the attacker is unauthenticated (PR:N) because CSRF abuses the VICTIM's session, and UI:R correctly reflects that a logged-in administrator must load attacker-controlled content for the forged GET to fire. No EPSS score, no CISA KEV listing, and no public exploit code are present in the intelligence, so this is 'no public exploit identified at time of analysis' - not active exploitation. Note the fix CHANGELOG uses the loaded phrase 'zero-interaction'; that means no click is required (an <img> tag auto-fetches the GET), but it still depends on the admin being authenticated and loading the malicious page, so the practical bar is higher than a fully drive-by remote exploit. The I:H rating is defensible but arguably overstated: the only effect is stopping recurring invoices, a bounded and administratively recoverable state change (the admin can re-enable billing), so the real-world impact is business disruption/financial-loss risk rather than deep data integrity compromise. Overall a real-but-not-urgent priority - patch on a normal cycle. |
| Exploit ScenarioDerived | An attacker crafts a web page (or email) embedding auto-loading resources such as <img src="https://victim-invoiceplane/invoices/recurring/stop/1"> repeated across many recurring-invoice IDs. When an authenticated InvoicePlane administrator visits that content, their browser silently issues the state-changing GET requests, stopping the targeted recurring invoices and interrupting billing. No public proof-of-concept is referenced, though the fix CHANGELOG explicitly describes the trivial <img>-tag technique. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 25, 2026
Cross-site request forgery in InvoicePlane versions prior to 1.7.2 lets an attacker silently stop a victim's recurring invoices by luring an authenticated administrator into loading attacker-controlled content that auto-requests the state-changing GET endpoint /invoices/recurring/stop/{id}. Because the route performs a privileged action without CSRF token validation on a simple GET, the attacker needs only a known or brute-forceable recurring-invoice identifier and no user interaction beyond the admin having a live session. The impact is integrity-only and confined to interrupting recurring billing, which can cause financial loss for the organization; the vendor has confirmed the flaw (GHSA-qf9q-2hxm-4wh9) and fixed it in release 1.7.2. No public exploit code has been identified and the issue is not listed as actively exploited in CISA KEV, though the low attack complexity and zero-click nature of the request keep the practical risk moderate.
RemediationAI
Upgrade to InvoicePlane 1.7.2, the vendor-released patch that converts the stop action to a POST form with CSRF token validation (release tag v1.7.2, PR #1636, commit 2c76ef5655c2c188110a9c1932338e6a3022ea20); the advisory at https://github.com/InvoicePlane/InvoicePlane/security/advisories/GHSA-qf9q-2hxm-4wh9 documents the issue. If immediate upgrade is not possible, compensating controls include: block or reject GET requests to /invoices/recurring/stop/* at the reverse proxy or WAF - note this also disables the legitimate stop button in the unpatched UI, so recurring invoices would need to be stopped at the database/config level until the patch is applied; set session cookies with SameSite=Strict (or Lax) and HttpOnly, understanding that Strict can break external SSO/OAuth redirects; restrict administrative access to InvoicePlane to trusted networks or an IP allowlist/VPN, which reduces the reachable attack surface but requires network changes for remote admins; and monitor application logs for unexpected recurring-invoice stop events and unusual Referer/Origin headers, since CSRF requests typically carry foreign or absent origins. Rotating administrator sessions after confirming a suspicious stop event limits continued abuse of a hijacked session.
Affected VersionsENISA
Affected Packages
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
InvoicePlane is a self-hosted PHP/CodeIgniter application for invoices, clients and payments, and the affected component is the Recurring invoices controller in the invoices module (CPE cpe:2.3:a:invoiceplane:invoiceplane:*:*:*:*:*:*:*:*, all versions below 1.7.2). The root cause is CWE-352 (Cross-Site Request Forgery): the Recurring::stop() action was implemented as a link-driven GET route (invoices/recurring/stop/{invoice_recurring_id}) rendered in partial_invoices_recurring_table.php, so any browser request carrying the administrator's session cookie is treated as an authorized state change. The upstream fix in PR #1636 changed the UI to a POST form and added CSRF token validation via _csrf_field(), plus a new ensure_valid_post_request('invoices/recurring/index') guard in the controller - the classic pattern of converting a state-changing GET into a POST with a per-session token. Because no token was required and no method restriction existed, no JavaScript or social engineering beyond an auto-fetching resource (e.g. an <img> tag) is needed once the admin is authenticated; the only enumeration constraint is knowing or guessing valid recurring-invoice IDs.
Know when Invoiceplane 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
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Classic CSRF: attacker unauthenticated (PR:N) abusing an authed admin who must load content (UI:R); impact is a bounded, recoverable billing-stop, so I:L rather than I:H, C/A:N.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
1DescriptionCVE.org
InvoicePlane is a self-hosted open source application for managing invoices, clients, and payments. Prior to 1.7.2, InvoicePlane 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. This issue is fixed in version 1.7.2.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Request Forgery exploits the automatic credential inclusion behavior of web browsers.
More in Invoiceplane
View allInvoicePlane through 1.6.3 allows authenticated users to upload PHP files as attachments that can be executed remotely.
Remote Code Execution in InvoicePlane self-hosted invoicing application through code injection. PoC and patch available.
InvoicePlane version 1.4.10 is vulnerable to a Arbitrary File Upload resulting in an authenticated user can upload a mal
In InvoicePlane 1.5.11 a misconfigured web server allows unauthenticated directory listing and file download. Rated high
Unauthenticated attackers can read arbitrary files from InvoicePlane servers through path traversal in the Guest control
An SQL injection vulnerability in InvoicePlane through 1.6.3 has been identified in "maxQuantity" and "minQuantity" para
InvoicePlane (all versions tested as of December 2024) v.1.6.11 and before contains a remote code execution vulnerabilit
Cross Site Scripting (XSS) vulnerability in InvoicePlane 1.6 via filter_product input to file modal_product_lookups.php.
An XSS issue was discovered in InvoicePlane 1.5.10 via the "Quote PDF Password(Optional)" field. Rated medium severity (
Stored XSS via SVG file upload in InvoicePlane 1.7.0 Login Logo functionality allows authenticated administrators to inj
Stored XSS in InvoicePlane 1.7.0's invoice editing function fails to sanitize the invoice_number parameter, allowing aut
Stored XSS in InvoicePlane 1.7.0 via malicious SVG file upload in the Invoice Logo function allows authenticated adminis
EUVD-2026-87124
NVD
CVE.org
EPSS
Vulnrichment
GitHub
Exploit-DB