Yes. org.apache.dolphinscheduler:dolphinscheduler-api (Maven): upgrade to 3.1.0 or later; org.apache.dolphinscheduler:dolphinscheduler-common (Maven): upgrade to 3.1.0 or later; org.apache.dolphinscheduler:dolphinscheduler-dao (Maven): upgrade to 3.1.0 or later; org.apache.dolphinscheduler:dolphinscheduler-service (Maven): upgrade to 3.1.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2023-49620?
Check whether you run org.apache.dolphinscheduler:dolphinscheduler-api (Maven), org.apache.dolphinscheduler:dolphinscheduler-common (Maven), org.apache.dolphinscheduler:dolphinscheduler-dao (Maven) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
org.apache.dolphinscheduler:dolphinscheduler-api (Maven): upgrade to 3.1.0 or later
# set org.apache.dolphinscheduler:dolphinscheduler-api to 3.1.0 in your pom.xml or build.gradle
org.apache.dolphinscheduler:dolphinscheduler-common (Maven): upgrade to 3.1.0 or later
# set org.apache.dolphinscheduler:dolphinscheduler-common to 3.1.0 in your pom.xml or build.gradle
org.apache.dolphinscheduler:dolphinscheduler-dao (Maven): upgrade to 3.1.0 or later
# set org.apache.dolphinscheduler:dolphinscheduler-dao to 3.1.0 in your pom.xml or build.gradle
org.apache.dolphinscheduler:dolphinscheduler-service (Maven): upgrade to 3.1.0 or later
# set org.apache.dolphinscheduler:dolphinscheduler-service to 3.1.0 in your pom.xml or build.gradle