CVE-2025-62421
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 · uneditedDataEase is a data visualization and analytics platform. In DataEase versions through 2.10.13, a stored cross-site scripting vulnerability exists due to improper file upload validation and authentication bypass. The StaticResourceApi interface defines a route upload/{fileId} that uses a URL path parameter where both the filename and extension of uploaded files are controllable by users. During permission validation, the TokenFilter invokes the WhitelistUtils#match method to determine if the URL path is in the allowlist. If the requestURI ends with .js or similar extensions, it is directly deemed safe and bypasses permission checks. This allows an attacker to access "upload/1.js" while specifying arbitrary file extensions, enabling the upload of HTML files containing malicious JavaScript. The vulnerability is fixed in version 2.10.14. No known workarounds exist.
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 confidenceDataEase versions through 2.10.13 contain a stored XSS vulnerability stemming from improper file upload validation combined with an authentication bypass. The StaticResourceApi upload/{fileId} endpoint allows users to control filename and extension. The TokenFilter's WhitelistUtils#match method incorrectly treats any requestURI ending with .js as safe, bypassing permission checks entirely. This enables attackers to upload HTML files containing malicious JavaScript through the upload endpoint.
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< 2.10.14CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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.
-
Identify installed DataEase versionCheck the DataEase application version banner, about page, or API metadata endpoint (typically accessible via /api/info or the admin dashboard). Compare the version number to the affected range.Affected if The installed version is any release prior to 2.10.14 (e.g., 2.10.13, 2.10.12, etc.).
-
Verify authentication bypass on upload endpointAttempt to access the StaticResourceApi upload endpoint (upload/{fileId}) without valid authentication credentials. Observe whether the request is processed or rejected.Affected if The endpoint accepts and processes requests without requiring valid authentication tokens.
-
Inspect WhitelistUtils configuration for .js extensionReview the TokenFilter's WhitelistUtils#match method configuration in the deployed application code or configuration files. Check if the whitelist logic grants unconditional access to any URI ending with .js.Affected if The WhitelistUtils#match method contains logic that treats all requestURIs ending with .js as safe, bypassing permission checks.
-
Review uploaded files for suspicious HTML contentExamine the file storage directory (typically the upload or static resource directory) for .html or .htm files. Inspect their contents for embedded <script> tags or malicious JavaScript.Affected if HTML files containing unauthorized JavaScript code are present in the upload directory.
-
Check access logs for anomalous upload patternsReview DataEase server access logs for POST requests to /api/staticResource/upload/* or similar upload endpoints originating from unauthenticated or low-privilege users.Affected if Logs show successful file uploads from users who should not have upload permissions.
A system is affected if it runs DataEase version 2.10.13 or earlier AND has the upload endpoint accessible without proper authentication due to the .js whitelist bypass.
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 · scoped2.10.14
Upgrade DataEase to version 2.10.14 or later, as no workarounds exist for this vulnerability.
Dataease 2.10.14
- 1. Back up the current Dataease installation and database.
- 2. Download Dataease version 2.10.14 from the official GitHub repository or release page.
- 3. Stop the Dataease service.
- 4. Upgrade the Dataease installation to version 2.10.14 following the standard upgrade procedure.
- 5. Verify the upgrade was successful by checking the version number.
- 6. Restart the Dataease service.
- 7. Test that the StaticResourceApi upload functionality works correctly and that permission checks are properly enforced for .js and other file extensions.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62421 — 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-62421 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