How severe is CVE-2022-34112?

CVE-2022-34112 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-34112?

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

How do I fix CVE-2022-34112?

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 CVE-2022-34112 is resolved across your whole dependency graph.

How do I detect CVE-2022-34112 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-2022-34112 if there is no patch (or I can't update yet)?

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.

Is CVE-2022-34112 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2022-34112, 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-2022-34112?

CVE-2022-34112 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 50th 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-2022-34112?

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

When was CVE-2022-34112 published, and has it been updated?

CVE-2022-34112 was published on July 22, 2022 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

MEDIUM severity

CVE-2022-34112 — dataease-plugin-common

MEDIUMFix: dataease/dataease@5f611d3

CVE-2022-34112 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.

Dataease before 1.11.2 access control issue allows attackers to arbitrarily uninstall plugin

Also known asGHSA-c2pj-rr68-pw94

Published

Jul 22, 2022

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs50th percentile — riskier than 50% 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

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

1 total 1 fixed

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

Affected Products

1 product · 1 configurations

Application

dataeasedataease

1 version

1.11.1

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.

An access control issue in the component /api/plugin/uninstall Dataease …

github.comNVDJul 2022

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.11.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-34112 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

O3 Security · Impact-Aware SCA

Is CVE-2022-34112 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

CWE Classification

CWE-732CWE-732

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

Timeline

Disclosed

Jul 22, 2022

First exploit

Jul 31, 2022

Last updated

Oct 28, 2026

Identifiers

CVE-2022-34112

GHSA-c2pj-rr68-pw94

References

Advisorygithub.com · CVE 2022 34112.json Advisorynvd.nist.gov · CVE 2022 34112 Reportgithub.com Webgithub.com · 5f611d3e3934816e9ad34e3d21807978001e2c8b Webgithub.com · v1.11.2 Packagegithub.com · dataease

Related vulnerabilities

Also affects dataease-plugin-common

This CVE is medium severity; 6 of 6 other CVEs affecting dataease-plugin-common are rated as high or higher (top: critical).

CVE-2023-40771CVE-2023-32310CVE-2022-39312CVE-2022-34113CVE-2022-34114CVE-2022-34115

Same weakness: CWE-732

This CVE is medium severity, in line with the other 2 CVEs with CWE-732.

CVE-2026-112908CVE-2026-112910Browse all CWE-732

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026

CVE-2022-34112 — dataease-plugin-common

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2022-34112 in your dependencies?