CWE-109: Struts: Validator Turned Off | Glexia
CWE-109 (Struts: Validator Turned Off) weakness overview with consequences, detection methods, mitigations, related CVEs and MITRE ATT&CK context.
Glexia's Take · Automated analysis
CWE-109: Struts: Validator Turned Off
Struts: Validator Turned Off represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Executive Impact
- Access Control: Bypass Protection Mechanism
Developer Pattern
CWE-109 is the kind of defect developers can usually prevent with explicit validation, safer framework defaults, and tests that exercise hostile input or unsafe state transitions.
Automation confidence
high confidence from CWE-109, 4.20.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Official CWE Definition
CWE-109: Struts: Validator Turned Off
Automatic filtering via a Struts bean has been turned off, which disables the Struts Validator and custom validation logic. This exposes the application to other weaknesses related to insufficient input validation.
Developer And Remediation Guidance
How teams prevent and detect this weakness
Causes
- This mapping defines an action for a download form: This mapping has disabled validation. Disabling validation exposes this action to numerous types of attacks.
Remediation
- Implementation: Ensure that an action form mapping enables validation. Set the validate field to true.
Detection
- Code review
- SAST
- DAST
- Focused regression tests
Mappings
Related CVEs, CWEs, and ATT&CK context
ATT&CK Relevance
ATT&CK relevance is shown only when reviewed or responsibly inferred.