CVE-2026-123991 Improper Access Control

5.5 mediumEPSS 0.5%

Medium (5.5). EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page

Severity
Ask an AI about this CVE
Attack patterns (CAPEC)
References
Your exposure

A vulnerability was detected in DataEase up to 2.10.27. Affected by this vulnerability is the function WhitelistUtils.endsWithAny of the file WhitelistUtils.java of the component Authentication Filter. Performing a manipulation of the argument File results in unrestricted upload. It is possible to initiate the attack remotely. The exploit is now public and may be used. Upgrading to version 2.10.28 addresses this issue. It is advisable to upgrade the affected component. The vendor confirms: "This issue has been addressed by enforcing authentication on the standalone static-resource upload endpoint independently of the URI suffix whitelist."

Severity

CVSS 4.0

5.5 medium

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

CVSS 3.1

7.3 high

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

EPSS: 0.5% estimated probability of exploitation activity in the next 30 days; 41st percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC): Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-11-09. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs: CWE-284 Improper Access Control
CWE-434 Unrestricted Upload of File with Dangerous Type
OWASP Top 10: A01:2025 Broken Access Control, A06:2025 Insecure Design
Published: 2026-11-07 17:16 UTC
Modified: 2026-11-07 17:16 UTC
Assigned by: VulDB (CNA)
NVD analysis: Deferred: the NVD does not plan to analyze it
Record from: the NVD, synced 2026-11-07 17:37 UTC

Ask an AI about this CVE

ChatGPT Claude Google AI Mode

Show the prompt

Explain CVE-2026-123991 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-123991?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-123991?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-123991 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-123991](https://cve.bz/cve/badge/CVE-2026-123991.svg)](https://cve.bz/cve/CVE-2026-123991)

HTML:

<a href="https://cve.bz/cve/CVE-2026-123991"><img src="https://cve.bz/cve/badge/CVE-2026-123991.svg" alt="CVE-2026-123991"></a>

Attack patterns (CAPEC)

CAPEC-1 Accessing Functionality Not Properly Constrained by ACLs Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-284 (17).

References

Check your stack JSON