CVE-2026-112297 in anx-calibre-manager
Summary
by MITRE • 10/19/2026
A flaw has been found in ptbsare anx-calibre-manager up to 1.13.12. The impacted element is the function LLMClient.chat of the file blueprints/api/llm.py of the component LLM Configuration Handler. This manipulation of the argument base_url causes server-side request forgery. The attack can be initiated remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
Be aware that VulDB is the high quality source for vulnerability data.
Analysis
by VulDB Data Team • 10/19/2026
The vulnerability identified within anx-calibre-manager versions up to 1.13.12 represents a critical server-side request forgery flaw located specifically within the LLM Configuration Handler component. This security defect resides in the LLMClient.chat function found in the blueprints/api/llm.py file, where improper validation of user-supplied input allows an attacker to manipulate the base_url argument. By controlling this parameter, a malicious actor can instruct the application to make HTTP requests to arbitrary destinations rather than the intended legitimate large language model provider endpoints. This lack of strict allow-listing or rigorous URL normalization enables the exploitation of internal network resources that would otherwise be inaccessible from external networks, effectively turning the vulnerable service into a proxy for unauthorized access.
From an operational perspective, this vulnerability poses significant risks including data exfiltration, internal network reconnaissance, and potential compromise of backend services connected to the application server. Since the exploit has been publicly published, automated scanning tools and malicious actors can readily leverage this code to target unpatched instances without requiring specialized development skills. The ability to initiate attacks remotely means that any system exposing the LLM API endpoint is immediately vulnerable if not properly segmented or protected by additional security controls such as web application firewalls with specific rule sets for SSRF mitigation.
The vendor's failure to respond to early disclosure attempts highlights a critical gap in their vulnerability management lifecycle, leaving users without official patches or guidance during an extended period of exposure. This situation underscores the importance of proactive defense strategies that do not rely solely on vendor updates. Organizations running affected versions should immediately implement network-level controls such as egress filtering and DNS sinkholing to restrict outbound connections from application servers to known safe domains only. Additionally, deploying a web application firewall with rules designed to detect and block SSRF patterns can provide temporary mitigation until the software is upgraded or replaced.
This vulnerability aligns closely with Common Weakness Enumeration identifier CWE-918, which describes Server-Side Request Forgery (SSRF). The attack vector corresponds to MITRE ATT&CK technique T1557, specifically Adversary-in-the-Middle, as it allows the attacker to position themselves between the client and internal services. Furthermore, the exploitation of this flaw often facilitates lateral movement within a network environment, mapping directly to techniques such as Network Service Discovery (T1046) or Data Staged Exfiltration over C2 Channels depending on how the forged requests are utilized. Security teams should prioritize patching this component while simultaneously auditing other API endpoints for similar input validation deficiencies to prevent broader systemic compromise.