CVE-2026-48083: OpenReception: Unauthenticated POST /api/log accepts arbitrary content with CRLF injection and no size or rate limits
OpenReception's appointment booking software provides an end-to-end encrypted appointment booking platform. Prior to version 1.0.2, the /api/log endpoint accepts unauthenticated POST requests, applies no schema validation to the message body, writes attacker-controlled content directly into the application's stdout log, interprets newline characters as real line breaks, and enforces no size or rate limits. Three independent abuse modes follow: log injection (forge log lines that look like legitimate system events), log volume DoS (saturate the logging pipeline at sustained 100+ requests per second of small messages), and oversized-payload submission (100 KB payloads accepted; larger sizes not tested). The most operationally damaging mode is log injection. An attacker can inject lines that an operator scanning logs would mistake for real system errors, mask their own activity behind fake noise, or pollute SIEM alerting rules with crafted false positives. A line such as [error]: injected admin error injected from an unauthenticated source is indistinguishable from the application's own error output once written to disk. Version 1.0.2 fixes the issue.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
OpenReception appointment booking software (/api/log CRLF/log injection)to a version that resolves this vulnerability.Fixed in 1.0.2
Event History
Frequently Asked Questions
What is the severity of CVE-2026-48083?
The severity of CVE-2026-48083 is medium with a score of 6.5.
How do I fix CVE-2026-48083?
To fix CVE-2026-48083, update OpenReception to version 1.0.2 or later.
What type of attack does CVE-2026-48083 allow?
CVE-2026-48083 allows for CRLF injection attacks through unauthenticated POST requests.
What are the potential impacts of CVE-2026-48083?
CVE-2026-48083 can lead to arbitrary content being written into the application logs, potentially allowing for further exploitation.
Is authentication required to exploit CVE-2026-48083?
No, authentication is not required to exploit CVE-2026-48083, making it particularly concerning.