Dataease before 1.11.2 access control issue allows attackers to arbitrarily uninstall pluginGHSA-c2pj-rr68-pw94
MEDIUMFix: dataease/dataease@5f611d3GHSA-c2pj-rr68-pw94 is a medium-severity (CVSS 6.5) CWE-732 vulnerability in io.dataease:dataease-plugin-common. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for io.dataease:dataease-plugin-common — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
io.dataease:dataease-plugin-commonReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
An access control issue in the component /api/plugin/uninstall Dataease v1.11.1 allows attackers to arbitrarily uninstall the plugin, a right normally reserved for the administrator. Version 1.11.2 contains a patch for this issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.dataease:dataease-plugin-common | all versions | 1.11.2io.dataease:dataease-plugin-common:1.11.2 |
Affected Products
dataeasedataeaseResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.dataease:dataease-plugin-common, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.dataease:dataease-plugin-common to 1.11.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c2pj-rr68-pw94 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is GHSA-c2pj-rr68-pw94 in your dependencies?
Find it across Maven, including transitive dependencies.