VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

io.dataease:dataease-plugin-common: vulnerability history, versions and safety

io.dataease:dataease-plugin-common is a package in the Maven ecosystem. Vulert records 7 vulnerabilities for it across 37 releases, from Jul 2022 to Sep 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
7 vulnerabilities recorded C3 H3 M1
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all io.dataease:dataease-plugin-common vulnerabilities

Vulert verdict on io.dataease:dataease-plugin-common 1.18.16 i

Updated on 23 Oct 2026

Careful: 1.18.16 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Niche
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 1.18.16 — affected i
  • Vulnerabilities on record 7 over 1 year · 0 in the last year i
  • Latest disclosure 01 Sep 2023 i
  • Highest CVSS 9.8 i
  • With no published fix 1 i
  • Stars 81,754 i
  • OpenSSF scorecard 6/10 i
  • Last release 31 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by Maven Central, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for io.dataease:dataease-plugin-common, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
1.18.16 08 Mar 2024 H1 — No Details →
1.18.15 01 Feb 2024 H1 — No Details →
1.18.14 03 Jan 2024 H1 — No Details →
1.18.13 07 Dec 2023 H1 — No Details →
1.18.12 01 Nov 2023 H1 — No Details →
1.18.11 15 Sep 2023 H1 — No Details →
1.18.10 13 Sep 2023 H1 — No Details →
1.18.9 28 Jul 2023 H1 Apache-2.0 No Details →
1.18.8 25 Jun 2023 H1 Apache-2.0 No Details →
1.18.7 02 Jun 2023 H1 Apache-2.0 No Details →
1.18.6 17 Apr 2023 H2 Apache-2.0 No Details →
1.18.5 23 Mar 2023 H2 Apache-2.0 No Details →
1.18.4 07 Mar 2023 H2 Apache-2.0 No Details →
1.18.3 23 Feb 2023 H2 Apache-2.0 No Details →
1.18.2 02 Feb 2023 H2 Apache-2.0 No Details →
1.18.1 11 Jan 2023 H2 Apache-2.0 No Details →
1.18.0 05 Jan 2023 H2 Apache-2.0 No Details →
1.17.0 01 Dec 2022 H2 Apache-2.0 No Details →
1.16.0 03 Nov 2022 H2 Apache-2.0 No Details →
1.15.0 08 Oct 2022 C1 H2 Apache-2.0 No Details →
1.14.0 01 Sep 2022 C1 H2 Apache-2.0 No Details →
1.13.0 04 Aug 2022 C1 H2 Apache-2.0 No Details →
1.12.0 06 Jul 2022 C1 H2 Apache-2.0 No Details →
1.11.3 27 Jun 2022 C1 H2 Apache-2.0 No Details →
1.11.1 06 Jun 2022 C3 H3 M1 Apache-2.0 No Details →
1.11.0 02 Jun 2022 C3 H3 M1 Apache-2.0 No Details →
1.10.0 05 May 2022 C3 H3 M1 Apache-2.0 No Details →
1.9.0 06 Apr 2022 C3 H3 M1 Apache-2.0 No Details →
1.8.0 03 Mar 2022 C3 H3 M1 Apache-2.0 No Details →
1.7 28 Jan 2022 C3 H3 M1 Apache-2.0 No Details →
1.6 04 Jan 2022 C3 H3 M1 Apache-2.0 No Details →
1.5 01 Dec 2021 C3 H3 M1 Apache-2.0 No Details →
1.4 03 Nov 2021 C3 H3 M1 Apache-2.0 No Details →
1.3 13 Oct 2021 C3 H3 M1 Apache-2.0 No Details →
1.2 02 Sep 2021 C3 H3 M1 Apache-2.0 No Details →
1.1 26 Jul 2021 C3 H3 M1 Apache-2.0 No Details →
1.0 23 Jul 2021 C3 H3 M1 Apache-2.0 No Details →

All 37 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 5
  • 2023 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 7 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for io.dataease:dataease-plugin-common

The 5 most severe of 7 vulnerabilities recorded for this package

Search all 7 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-34113: Arbitrary Code Execution in Dataease Plugin 9.8 critical 1.11.2 23 Jul 2022
CVE-2022-34115: SQL Injection in Dataease v1.11.1 via parameter dataSourceId 9.8 critical 1.11.2 23 Jul 2022
CVE-2022-39312: MySQL JDBC deserialization vulnerability in io.dataease:dataease-plugin-common 9.8 critical 1.15.2 18 Oct 2022
CVE-2022-34114: SQL Injection in Dataease 8.8 high 1.11.2 23 Jul 2022
CVE-2023-32310: DataEase API interface IDOR vulnerability in io.dataease:dataease-plugin-common 8.1 high 1.18.7 02 Jun 2023

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About io.dataease:dataease-plugin-common

Is io.dataease:dataease-plugin-common safe to use?

Vulert records 7 vulnerabilities for io.dataease:dataease-plugin-common in Maven: 3 critical, 3 high, 1 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is io.dataease:dataease-plugin-common's Vulert package health score?

Vulert scores io.dataease:dataease-plugin-common 60/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of io.dataease:dataease-plugin-common affected?

Yes. 1.18.16, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of io.dataease:dataease-plugin-common should I use?

1.18.16 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does io.dataease:dataease-plugin-common have?

7 vulnerabilities are recorded for io.dataease:dataease-plugin-common in the Maven ecosystem: 3 critical, 3 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new io.dataease:dataease-plugin-common vulnerabilities disclosed?

0 vulnerabilities were recorded for io.dataease:dataease-plugin-common in the last 12 months, and the oldest entry in this database dates to 23 Jul 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of io.dataease:dataease-plugin-common are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor io.dataease:dataease-plugin-common for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the io.dataease:dataease-plugin-common version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.