dbcve.org
SkycaijiApplication

CVE-2025-1799

MEDIUM · 6.3 CVSS v3.1 Published 2025-03-01
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, which was classified as critical, was found in Zorlan SkyCaiji 2.9. This affects the function previewAction of the file vendor/skycaiji/app/admin/controller/Tool.php. The manipulation of the argument data leads to server-side request forgery. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.

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

Zorlan SkyCaiji 2.9 contains a server-side request forgery (SSRF) vulnerability in the previewAction function of vendor/skycaiji/app/admin/controller/Tool.php. The vulnerability allows remote attackers to induce the server to make arbitrary HTTP requests to internal or external resources via manipulation of the 'data' argument.

MitigationImplement strict input validation and allowlist validation for the 'data' parameter in the previewAction function to ensure only permitted URLs/domains can be accessed. Consider implementing network segmentation and disabling unnecessary outbound connections from the server.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SkycaijiApplication
Affected:= 2.9

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. Verify Skycaiji version 2.9 is installed
    Locate and read the version file or configuration file (such as version.php, config.php, or composer.json) in the Skycaiji installation directory to confirm the installed version is exactly 2.9
    Affected if The installed version is 2.9 and matches the affected version range
  2. Confirm vulnerable Tool.php controller exists
    Check if the file vendor/skycaiji/app/admin/controller/Tool.php exists in the Skycaiji installation directory
    Affected if The file exists and the server is running Skycaiji 2.9
  3. Verify previewAction function is present
    Examine the Tool.php file and locate the previewAction function to confirm it handles the 'data' parameter
    Affected if The previewAction function exists and processes the 'data' parameter
  4. Check tool endpoint accessibility
    Identify the web route that maps to the Tool controller's previewAction (typically under /admin/tool/preview or similar admin routing) and determine if it is accessible without authentication or from untrusted networks
    Affected if The endpoint is accessible without proper authentication or from untrusted sources
  5. Inspect current input validation on 'data' parameter
    Review the previewAction function code to determine if the 'data' parameter undergoes strict allowlist validation before being used in HTTP requests
    Affected if No strict allowlist validation exists for the 'data' parameter, allowing arbitrary URLs

A user is affected if running Skycaiji version 2.9 with the Tool.php controller present and the previewAction endpoint accessible without strict validation on the 'data' parameter.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and allowlist validation for the 'data' parameter in the previewAction function to ensure only permitted URLs/domains can be accessed. Consider implementing network segmentation and disabling unnecessary outbound connections from the server.

Fix this in Skycaiji Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1799 — 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-1799 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