dbcve.org
InjectionWeakness · CWE-74

CVE-2025-14674

MEDIUM · 6.3 CVSS v3.1 Published 2025-12-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability was found in aizuda snail-job up to 1.6.0. Affected by this vulnerability is the function QLExpressEngine.doEval of the file snail-job-common/snail-job-common-core/src/main/java/com/aizuda/snailjob/common/core/expression/strategy/QLExpressEngine.java. The manipulation results in injection. The attack can be launched remotely. Upgrading to version 1.7.0-beta1 addresses this issue. The patch is identified as 978f316c38b3d68bb74d2489b5e5f721f6675e86. The affected component should be upgraded.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A code injection vulnerability exists in the QLExpressEngine.doEval function within snail-job. The affected component processes QLExpress expressions without proper sanitization, allowing remote attackers to inject malicious expression statements that could lead to arbitrary code execution.

MitigationUpgrade snail-job to version 1.7.0-beta1 or later which contains the patch (commit 978f316c38b3d68bb74d2489b5e5f721f6675e86) that addresses the injection vulnerability in the QLExpress expression handling.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify snail-job installation and version
    Locate the snail-job installation directory and check the version file (commonly version.txt, pom.xml, or the JAR manifest). On Linux, search in /opt, /usr/share, or application deployment directories. On Windows, check Program Files or custom application paths.
    Affected if The installed version is earlier than 1.7.0-beta1 (any 1.x version prior to the beta1 release).
  2. Confirm QLExpressEngine is in use
    Search configuration files (application.yml, application.properties) for 'QLExpress' or 'express' related settings. Also inspect the codebase for imports of com.qlexpressengine or calls to QLExpressEngine.doEval method.
    Affected if QLExpressEngine is configured or the doEval function is present in the codebase, indicating the vulnerable component is active.
  3. Check exposure of the vulnerable endpoint
    Review API endpoints or scheduled tasks that invoke QLExpressEngine.doEval. Look for REST controllers, message consumers, or job schedulers that accept user input and pass it to expression evaluation.
    Affected if The doEval function processes untrusted input from network-facing APIs, message queues, or user-submitted data without validation.

You are affected if snail-job version is below 1.7.0-beta1 AND the QLExpressEngine.doEval function is exposed to untrusted input.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade snail-job to version 1.7.0-beta1 or later which contains the patch (commit 978f316c38b3d68bb74d2489b5e5f721f6675e86) that addresses the injection vulnerability in the QLExpress expression handling.

Recommended fix High confidence

1.7.0-beta1

  1. 1. Identify all projects and modules that depend on snail-job-common-core or the snail-job parent pom
  2. 2. Locate the pom.xml or build configuration file that declares the snail-job dependency
  3. 3. Update the version of com.aizuda:snail-job-common-core (or the snail-job pom) from 1.6.0 or earlier to 1.7.0-beta1
  4. 4. Run Maven/Gradle dependency resolution to fetch the new version
  5. 5. Rebuild the application and run unit/integration tests, particularly any tests covering expression evaluation
  6. 6. Verify the QLExpressEngine.doEval functionality works as expected with the new library version
  7. 7. Deploy the updated application to your test environment first
  8. 8. After validation, deploy to production
Caveat Beta version; review release notes for any breaking changes before upgrading production systems

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14674 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-14674 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data