How severe is CVE-2023-32310?

CVE-2023-32310 has a CVSS score of 8.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2023-32310?

CVE-2023-32310 affects the following packages: io.dataease:dataease-plugin-common (Maven). Ecosystems affected: Maven.

How do I fix CVE-2023-32310?

Update io.dataease:dataease-plugin-common to 1.18.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-32310 is resolved across your whole dependency graph.

How do I detect CVE-2023-32310 in my Maven dependencies?

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.

How do I mitigate CVE-2023-32310 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2023-32310 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2023-32310, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2023-32310?

CVE-2023-32310 has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 63th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2023-32310?

CVE-2023-32310 is classified as CWE-639 (CWE-639). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2023-32310 published, and has it been updated?

CVE-2023-32310 was published on June 1, 2023 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2023-32310 — dataease-plugin-common

HIGHFix: dataease/dataease@72f428e

CVE-2023-32310 is a high-severity (CVSS 8.1) CWE-639 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.

DataEase API interface has IDOR vulnerability

Also known asGHSA-7hv6-gv38-78wj

Published

Jun 1, 2023

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for CVE-2023-32310.

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs63th percentile — riskier than 63% of all scored CVEsHighest risk

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

1 pkg affected

☕io.dataease:dataease-plugin-common

Real-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

Impact

The api interface for DataEase delete dashboard and delete system messages is vulnerable to IDOR.

The interface to delete the dashboard:

Create two users: user1 and user2
User1 creates a dashboard named pan1
User2 creates a dashboard named pan2
Both user1 and user2 share their dashboards with the demo user
User1 wants to delete his dashboard. We hijack the request with burpsuite. The request will probably look like this: POST /api/share/removePanelShares/440efa7f-efd8-11ed-bec7-1144724bc08c HTTP/1.1. 440efa7f-efd8-11ed-bec7-1144724bc08c is the ID of pan1
We replace this ID with the ID of pan2 and continue the execution (i.e. we delete the shares of others)
Successfully remove the shared link

The interface to delete system messages:

Our request to delete a message is shown below
We can delete all messages by simply enumerating the message ID, regardless of whether the message belongs to the requester or not.
The interface for marking read messages is also affected

Affected versions: <= 1.18.6

Patches

The vulnerability has been fixed in v1.18.7.

Workarounds

It is recommended to upgrade the version to v1.18.7.

References

If you have any questions or comments about this advisory:

Open an issue in https://github.com/dataease/dataease Email us at [email protected]

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`io.dataease:dataease-plugin-common`	all versions	1.18.7`io.dataease:dataease-plugin-common:1.18.7`

Affected Products

1 product · 1 configurations

Application

dataeasedataease

< 1.18.7

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

DataEase is an open source data visualization and analysis tool. The API…

github.comNVDJun 2023

Detection & mitigation playbook

Open-source dependency

Detect
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.18.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-32310 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact The api interface for DataEase delete dashboard and delete system messages is vulnerable to IDOR. The interface to delete the dashboard: 1. Create two users: user1 and user2 2. User1 creates a dashboard named pan1 3. User2 creates a dashboard named pan2 4. Both user1 and user2 share their dashboards with the demo user 5. User1 wants to delete his dashboard. We hijack the request with burpsuite. The request will probably look like this: POST /api/share/removePanelShares/440efa7f-efd8-11ed-bec7-1144724bc08c HTTP/1.1. 440efa7f-efd8-11ed-bec7-1144724bc08c is the ID of pan1 6. We replac