Audit-log forgery via unsanitized cron key
Published Sep 25, 2026 · Updated Sep 25, 2026
Log injection in InvoicePlane before 1.7.2 allows remote attackers to forge audit entries through a crafted cron key in the URL path. Cron::recur() concatenates an invalid user-supplied cron key into an error-level log message without neutralizing CRLF characters. The unauthenticated cron endpoint is sufficient to corrupt forensic records or interfere with log-based monitoring, without reported data disclosure or service interruption.
Summary
What happened
Log injection in InvoicePlane before 1.7.2 allows remote attackers to forge audit entries through a crafted cron key in the URL path. Cron::recur() concatenates an invalid user-supplied cron key into an error-level log message without neutralizing CRLF characters. The unauthenticated cron endpoint is sufficient to corrupt forensic records or interfere with log-based monitoring, without reported data disclosure or service interruption.
The record
- CVE
- CVE-2026-85290
- Published
- Sep 25, 2026
- Updated
- Sep 25, 2026
- Vendor
- InvoicePlane
- Product
- InvoicePlane
- Classifications
- CWE-117, T1070
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 25, 2026CVE publishedPublication date reported by the CVE source.
- Sep 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.7.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Public exploit references
- Vendor-published CRLF cron-key requestproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started