Summary
FACTION's Struts2 AccessControlInterceptor failed to enforce authentication before invoking actions, and several BoilerPlateConfig actions did not perform any local session checks.
As a result, an unauthenticated attacker could read, overwrite, deactivate, or permanently delete any boilerplate template in the system simply by calling the exposed endpoints.
Affected context
This vulnerability appears in FACTION deployments where the Struts2-based web interface is exposed and relies on AccessControlInterceptor for global authentication.
The affected code path sits in front of BoilerPlateConfig actions that manage boilerplate templates used in pentesting report generation.
Because the interceptor and specific controller methods do not validate an active session, any party capable of reaching these endpoints over HTTP can interact with boilerplate templates without logging in.
Exploit preconditions
- Attack surface: FACTION web interface endpoints backed by Struts2 BoilerPlateConfig actions.
- Required access: Network-level access to the FACTION application (e.g., via HTTP(S)); no valid session or credentials are required.
- Trigger point: Direct invocation of BoilerPlateConfig actions that handle reading, updating, deactivating, or deleting boilerplate templates.
- Why exploitation is possible: AccessControlInterceptor unconditionally calls
invocation.invoke()without verifying session validity, and the affected actions do not perform independent session checks, effectively disabling authentication for these endpoints.
Why this happens
The underlying bug is a classic missing authentication check on sensitive application actions.
AccessControlInterceptor, intended to act as a centralized authentication gate for all Struts2 actions, calls the downstream action (invocation.invoke()) regardless of whether a valid session exists.
The impacted BoilerPlateConfig methods further assume that any request reaching them is already authenticated and therefore omit local session or authorization checks.
This combination maps directly to CWE-306 (Missing Authentication for Critical Function), where critical functions—here, template read/write/deletion—are exposed without ensuring that the caller is an authenticated user.
Potential impact
- An unauthenticated attacker could read any boilerplate template, exposing internal report structures and potentially sensitive template content.
- An attacker could overwrite existing templates, injecting malicious or misleading text into future pentest reports.
- Boilerplate templates could be deactivated to disrupt normal reporting workflows and degrade service availability.
- Templates could be permanently deleted, causing data loss and necessitating manual reconstruction of reporting assets.
- Compromised or manipulated templates could undermine trust in generated reports and introduce reputational damage.
General mitigation guidance
Effective mitigation focuses on consistently enforcing authentication and authorization at all layers that handle critical functions.
Common defensive patterns include:
- Ensuring that global interceptors or middleware responsible for authentication always verify session or token validity before invoking downstream actions.
- Adding explicit, local session checks within controller/action methods for operations that manage or alter shared configuration or content.
- Implementing role-based access controls so that only appropriately privileged, authenticated users may create, edit, deactivate, or delete templates.
- Applying a "secure by default" stance, where new actions and controllers are denied by default until explicit authentication and authorization policies are wired in.
- Centralizing security configuration and regularly reviewing it to avoid bypass paths, especially when new actions or modules are introduced.
How teams detect issues like this
Detection can leverage both preventive and retrospective techniques:
- Static analysis: Configure rules to flag Struts2 actions or controllers that lack explicit authentication/authorization checks or that bypass established interceptors.
- Code review: During peer review, treat all actions that modify shared resources (like configuration or templates) as high-risk and require visible, explicit access control logic.
- Security testing: Include unauthenticated fuzzing and endpoint discovery in QA and security testing pipelines to detect actions responding successfully without a session.
- Logging and monitoring: Enable detailed audit logs for template-related actions and set alerts for suspicious patterns, such as template deletions or edits originating from unauthenticated sources or unexpected IP ranges.

