Missing XML Validation vulnerability in Apache Struts, Apache Struts.
This issue affects Apache Struts: from 2.0.0 before 2.2.1; Apache Struts: from 2.2.1 through 6.1.0.
Users are recommended to upgrade to version 6.1.1, which fixes the issue.
Security readout for executives and security teams
Plain-English summary
Apache Struts has a high-severity XML External Entity issue in an outdated XWork component. Affected applications may expose sensitive data or be disrupted if they process crafted XML. Apache recommends upgrading to Struts 6.1.1.
Executive priority
Treat this as a near-term remediation item for any business-critical or internet-facing Struts application. No active exploitation is shown in the provided sources, but the affected range is broad and impact can be high.
Technical view
CVE-2025-68493 is a missing XML validation issue mapped to CWE-112 and CWE-611. It affects Apache Struts from 2.0.0 before 2.2.1 and 2.2.1 through 6.1.0. CVSS 3.1 is 8.1 with network access, low complexity, no privileges, and user interaction required.
Likely exposure
Exposure is most likely in Java web applications still running Apache Struts 2.x through 6.1.0, especially where XWork XML processing remains reachable.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The CVSS vector indicates remote attack potential, low complexity, no privileges, and required user interaction.
Researcher notes
Evidence supports an XXE-class flaw in the outdated XWork component with confidentiality and availability impact. The bundle does not provide exploit details, affected endpoints, or product-specific backports, so validation should focus on dependency presence and vendor advisories.
Mitigation direction
Upgrade Apache Struts to version 6.1.1 or later.
Inventory applications using com.opensymphony:xwork or org.apache.struts.xwork:xwork-core.
Prioritize internet-facing Struts applications and XML-handling workflows.
Check Apache S2-069 and vendor distribution guidance for deployment-specific fixes.
Apply compensating controls only as temporary risk reduction.
Validation and detection
Confirm deployed Apache Struts versions across production and build manifests.
Check dependency trees for legacy XWork packages named in the advisory.
Verify upgraded applications load Struts 6.1.1 or later at runtime.
Review logs for suspicious XML parsing errors or abnormal request patterns.
Track Red Hat advisories if using vendor-packaged Struts components.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-112: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-112 · source CWE mapping
Missing XML Validation
Missing XML Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Restriction of XML External Entity Reference
Improper Restriction of XML External Entity Reference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.