CVE-2025-49002
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 an open source business intelligence and data visualization tool. Versions prior to version 2.10.10 have a flaw in the patch for CVE-2025-32966 that allow the patch to be bypassed through case insensitivity because INIT and RUNSCRIPT are prohibited. The vulnerability has been fixed in v2.10.10. No known workarounds are available.
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 prior to 2.10.10 contain a security control bypass vulnerability. The patch for CVE-2025-32966 attempted to block INIT and RUNSCRIPT commands but performs case-sensitive matching, allowing attackers to bypass the restriction using case variants such as 'init' or 'runscript'. This leads to unauthorized command execution with critical severity.
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.10CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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.
-
Check DataEase versionLocate the DataEase installation and determine the installed version number. Common methods include checking the about page in the web UI, reviewing installation logs, or querying the API endpoint that returns version information.Affected if The installed version is any release before 2.10.10 (e.g., 2.10.9, 2.10.0, 1.x.x series)
-
Identify if script execution features are enabledReview DataEase configuration files and settings to determine whether features that allow running scripts or initialization commands are active. Look for settings related to query execution, script runners, or plugin functionalities that could invoke INIT or RUNSCRIPT commands.Affected if Script execution or query features that can invoke INIT or RUNSCRIPT commands are enabled in the configuration
-
Inspect command filter configurationsExamine any security filters, web application firewall rules, or input validation configurations that are meant to block INIT and RUNSCRIPT commands. Look for case-sensitive filters that may only block the uppercase variants.Affected if The filters or validation rules only block exact-case strings like 'INIT' and 'RUNSCRIPT' and do not handle case variations like 'init' or 'runscript'
-
Review recent query or execution logsSearch DataEase logs and audit trails for any executed commands that may indicate exploitation attempts or successful use of case-variation bypasses. Look for lowercase or mixed-case variants of INIT and RUNSCRIPT.Affected if Logs show evidence of script execution commands being run through case variations, indicating the bypass may have been used
You are affected if your DataEase version is below 2.10.10 and your environment allows script execution features that could invoke INIT or RUNSCRIPT commands, especially if your command filters are case-sensitive.
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.10
Upgrade to DataEase version 2.10.10 or later to remediate this vulnerability, as no workarounds are available.
2.10.10
- 1. Back up the existing Dataease installation and all associated databases
- 2. Stop the Dataease service
- 3. Download version 2.10.10 from the official Dataease repository or release page
- 4. Install version 2.10.10 following the standard Dataease upgrade procedure
- 5. Verify the upgrade was successful by checking the Dataease version
- 6. Restart the Dataease service
- 7. Test that core functionality works correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49002 — 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-49002 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