How severe is CVE-2023-49620?

CVE-2023-49620 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-2023-49620?

CVE-2023-49620 affects the following packages: org.apache.dolphinscheduler:dolphinscheduler-api (Maven), org.apache.dolphinscheduler:dolphinscheduler-common (Maven), org.apache.dolphinscheduler:dolphinscheduler-dao (Maven), org.apache.dolphinscheduler:dolphinscheduler-service (Maven). Ecosystems affected: Maven.

How do I fix CVE-2023-49620?

Update org.apache.dolphinscheduler:dolphinscheduler-api to 3.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-49620 is resolved across your whole dependency graph.

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

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.dolphinscheduler:dolphinscheduler-api, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2023-49620 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-2023-49620 actively exploited in the wild?

No public exploit code has been indexed for CVE-2023-49620 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

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

CVE-2023-49620 has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 67th 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-49620?

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

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

CVE-2023-49620 was published on November 30, 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

MEDIUM severity

CVE-2023-49620 — dolphinscheduler-api

MEDIUMFix: apache/dolphinscheduler#10307

CVE-2023-49620 is a medium-severity (CVSS 6.5) CWE-862 vulnerability in org.apache.dolphinscheduler:dolphinscheduler-api. A fix is available for org.apache.dolphinscheduler:dolphinscheduler-api — see the affected versions and patch details below.

Apache DolphinScheduler: Authenticated users could delete UDFs in resource center they were not authorized for

Also known asGHSA-r44q-98gx-pmh2

Published

Nov 30, 2023

Updated

Oct 28, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk0.00%

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

4 pkgs affected

☕org.apache.dolphinscheduler:dolphinscheduler-api☕org.apache.dolphinscheduler:dolphinscheduler-common☕org.apache.dolphinscheduler:dolphinscheduler-dao☕org.apache.dolphinscheduler:dolphinscheduler-service

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

Before DolphinScheduler version 3.1.0, the login user could delete UDF function in the resource center unauthorized (which almost used in sql task), with unauthorized access vulnerability (IDOR), but after version 3.1.0 we fixed this issue. We mark this cve as moderate level because it still requires user login to operate, please upgrade to version 3.1.0 to avoid this vulnerability

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.dolphinscheduler:dolphinscheduler-api`	all versions	3.1.0`org.apache.dolphinscheduler:dolphinscheduler-api:3.1.0`
☕Maven	`org.apache.dolphinscheduler:dolphinscheduler-common`	all versions	3.1.0`org.apache.dolphinscheduler:dolphinscheduler-common:3.1.0`
☕Maven	`org.apache.dolphinscheduler:dolphinscheduler-dao`	all versions	3.1.0`org.apache.dolphinscheduler:dolphinscheduler-dao:3.1.0`
☕Maven	`org.apache.dolphinscheduler:dolphinscheduler-service`	all versions	3.1.0`org.apache.dolphinscheduler:dolphinscheduler-service:3.1.0`

Affected Products

1 product · 1 configurations

Application

dolphinschedulerapache

< 3.1.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.dolphinscheduler:dolphinscheduler-api, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.dolphinscheduler:dolphinscheduler-api to 3.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-49620 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-2023-49620 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-862CWE-862

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Nov 30, 2023

Last updated

Oct 28, 2026

Identifiers

CVE-2023-49620

GHSA-r44q-98gx-pmh2

References

Advisorygithub.com · CVE 2023 49620.json Advisorylists.apache.org · zm4t1ykj4cro1c8183q7y32z0yzfz8yj Advisorynvd.nist.gov · CVE 2023 49620 Fixgithub.com Webopenwall.com Webgithub.com · a4948f58e671ab263060da1de255af3ecd2530ac Packagegithub.com · dolphinscheduler

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs affecting dolphinscheduler-api are rated as high or higher (top: critical).

CVE-2026-47340CVE-2026-32967CVE-2026-32966CVE-2026-41280CVE-2026-42357CVE-2023-49068CVE-2023-25601CVE-2020-13922

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026

CVE-2023-49620 — dolphinscheduler-api

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-2023-49620 in your dependencies?