CVE-2026-129173 in Stirling-PDF
Summary
by MITRE • 11/14/2026
A security flaw has been discovered in Stirling-Tools Stirling-PDF up to 3.3.0. Affected is the function WorkflowParticipantController.getParticipantDetails of the file app/proprietary/src/main/java/stirling/software/proprietary/workflow/controller/WorkflowParticipantController.java of the component Participant Details Endpoint. Performing a manipulation results in insufficient session timeout value. Remote exploitation of the attack is possible. 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 • 11/14/2026
The vulnerability identified within Stirling-PDF versions up to 3.3.0 represents a significant security deficiency rooted in improper session management mechanisms, specifically located within the WorkflowParticipantController.getParticipantDetails endpoint found in app/proprietary/src/main/java/stirling/software/proprietary/workflow/controller/WorkflowParticipantController.java. This component is responsible for retrieving details about workflow participants and serves as an entry point where authentication state validation occurs. The core technical flaw involves a misconfiguration or implementation error that results in insufficient session timeout values, allowing active sessions to persist far beyond acceptable security thresholds. In standard secure application design, session tokens should expire after a short period of inactivity or within a defined maximum lifetime to limit the window of opportunity for attackers who may have obtained valid credentials through phishing, keylogging, or other credential theft techniques. By failing to enforce strict timeout policies, the application retains active authentication states indefinitely unless explicitly logged out by the user, thereby increasing the risk of session hijacking and unauthorized access.
From an operational impact perspective, this flaw enables remote exploitation without requiring physical proximity or local system access, classifying it as a remotely exploitable vulnerability. An attacker who has acquired valid session cookies or tokens can maintain persistent access to the application interface for extended periods, potentially leading to data exfiltration, modification of workflow configurations, or unauthorized execution of document processing tasks within the Stirling-PDF environment. Since this endpoint deals with participant details in a collaborative workflow context, compromised sessions could allow an attacker to impersonate legitimate users, manipulate task assignments, or access sensitive documents associated with those participants. The lack of response from the vendor further exacerbates the risk profile, as affected organizations are left without official patches or guidance on remediation timelines, necessitating immediate proactive measures by system administrators and security teams responsible for deploying this software.
This vulnerability aligns closely with CWE-613, which describes insufficient session expiration, a common weakness in web applications where sessions remain active longer than necessary to perform their intended function. Additionally, the exploitation of such flaws often facilitates subsequent attacks categorized under MITRE ATT&CK technique T1078, Valid Accounts, particularly when attackers leverage stolen or guessed credentials to maintain persistent access within an environment. The absence of automatic session invalidation means that even if a user changes their password, existing active sessions may remain valid depending on the specific implementation details of the token validation logic, further complicating incident response efforts. Security practitioners should treat this as a high-priority issue requiring immediate attention due to its remote exploitability and the potential for long-term unauthorized access within enterprise document management workflows.
Mitigation strategies must focus on both technical controls and procedural adjustments until an official patch is released by the vendor. Administrators should implement reverse proxy configurations or web application firewall rules that enforce strict session timeout policies at the infrastructure level, ensuring that HTTP requests are validated against a maximum age constraint regardless of the application's internal logic. Additionally, enabling automatic logout mechanisms after periods of inactivity and restricting cookie attributes such as HttpOnly and Secure flags can reduce the surface area for session hijacking attacks. Organizations should also review access logs for anomalous activity patterns indicative of long-lived sessions being abused by unauthorized actors. Given the vendor's lack of engagement, stakeholders are advised to consider alternative solutions or forked versions with active maintenance if continuous availability is critical, while simultaneously applying network-level controls to mitigate the immediate risk posed by this insufficient session timeout vulnerability.