StrutsFramework / library · Apache
CVE-2025-68493
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMissing 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceMissing XML validation in Apache Struts allows attackers to potentially exploit XML parsing weaknesses. The vulnerability exists across a broad range of versions from 2.0.0 through 6.1.0, where XML input is not properly validated before processing.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
StrutsFramework / library
>= 2.0.0, <= 2.3.37>= 2.5.0, <= 2.5.33>= 6.0.0, < 6.1.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine installed Struts versionInspect your project's pom.xml for the struts2-core dependency version, or check the lib directory of your deployed WAR file for struts2-core-*.jar and note the version number.Affected if The version falls within 2.0.0-2.3.37, 2.5.0-2.5.33, or 6.0.0-6.1.0.
-
Identify XML upload or parsing usageSearch your codebase for references to FileUploadInterceptor, XStream deserialization, or any custom XML parsing logic in your action classes. Review struts.xml for <interceptor-ref name="fileUpload"/> or custom interceptor stacks handling XML content.Affected if Your application accepts XML file uploads or parses XML content through Struts interceptors or custom handlers.
-
Locate XML-consuming endpointsReview your struts.xml and action classes for any actions that accept multipart file uploads, form parameters containing XML, or REST endpoints with XML content-types (application/xml, text/xml).Affected if Any endpoint accepts XML payloads via HTTP requests.
-
Verify XXE protection configurationCheck your application for XML parser configuration. Look for DocumentBuilderFactory or XMLStreamReader instantiation in your code or library dependencies. Verify whether external entity processing is explicitly disabled.Affected if XML parsers are not configured to disable external entities, or no XXE protection is documented in your application configuration.
You are affected if your Struts version is within the vulnerable ranges AND your application accepts or parses XML content through Struts components.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped6.1.1
Upgrade Apache Struts to version 6.1.1, which contains the missing XML validation fix.
Struts 6.1.1 (or latest stable 6.x release)
- 1. Identify the current Apache Struts version in use by checking project dependencies or library files
- 2. For Struts 2.0.0 - 2.3.x branch: upgrade directly to Struts 6.1.1 or latest 6.x release
- 3. For Struts 2.5.x branch: upgrade directly to Struts 6.1.1 or latest 6.x release
- 4. For Struts 6.0.x branch: upgrade to Struts 6.1.1
- 5. Update all Struts-related dependencies in build configuration (Maven pom.xml, Gradle build.gradle, or library files)
- 6. Test application functionality in a non-production environment to verify compatibility
- 7. Review application for any deprecated API usage that may break after upgrade
- 8. Deploy the upgraded application to production
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Struts
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-68493 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-68493 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data