Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5

DataEase vulnerable to SQL injection

CVE-2023-40771GHSA-8rv7-g772-pp3j

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Maven io.dataease:dataease-plugin-common

    Affected
    <= 1.18.9
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
  • CVE-2023-40771: 0.98% estimated exploitation activity in the next 30 days; percentile 62.28 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

SQL injection vulnerability in DataEase v.1.18.9 allows a remote attacker to obtain sensitive information via a crafted string outside of the blacklist function.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-8rv7-g772-pp3j

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-40771

Advisory: DataEase vulnerable to SQL injection
IDs: CVE-2023-40771, GHSA-8rv7-g772-pp3j
Record: https://patchnext.com/advisories/cve-2023-40771 (revision 1, source checked 26 Oct 2026, 16:16 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven io.dataease:dataease-plugin-common: affected <= 1.18.9

## Suggested inspection (read-only)
- Maven io.dataease:dataease-plugin-common: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on io.dataease:dataease-plugin-common.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-8rv7-g772-pp3j (GitHub-reviewed advisory GHSA-8rv7-g772-pp3j lists affected ranges: Maven io.dataease:dataease-plugin-common >=0 <=1.18.9)

Commands are suggestions: review each one before running it.

Loading voting…