dbcve.org
MaccmsApplication

CVE-2025-10395

HIGH · 7.2 CVSS v3.1 Published 2025-09-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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 Magicblack MacCMS 2025.1000.4050. Affected by this vulnerability is the function col_url of the component Scheduled Task Handler. Performing manipulation of the argument cjurl results in server-side request forgery. It is possible to initiate the attack remotely.

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

Server-Side Request Forgery (SSRF) vulnerability in Magicblack MacCMS 2025's Scheduled Task Handler. The col_url function fails to properly validate the cjurl parameter, allowing authenticated remote attackers to manipulate the server into making arbitrary HTTP requests to internal or external resources. This could enable internal network reconnaissance, access to cloud metadata services, or pivoting to internal systems.

MitigationImplement strict allowlist-based validation for the cjurl parameter to restrict URLs to expected domains/paths only. Additionally, restrict outbound network access from the application server and disable the Scheduled Task Handler if not required.

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
MaccmsApplication
Affected:= 10.0

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 MacCMS version
    Locate the version file or admin panel footer that displays the installed MacCMS version number
    Affected if The installed version is exactly 10.0 (Magicblack MacCMS 2025)
  2. Locate the Scheduled Task Handler
    Search the application codebase for files related to scheduled tasks, task management, or the col_url function. Check for paths containing 'task', 'cron', 'schedule', or 'cjurl'
    Affected if The Scheduled Task Handler module exists and is accessible in the installation
  3. Verify col_url function implementation
    Open the file containing the col_url function and inspect how the cjurl parameter is processed. Look for any input validation, sanitization, or allowlist logic applied to this parameter
    Affected if The col_url function accepts the cjurl parameter without proper validation or allowlist filtering
  4. Check for authentication requirements
    Determine if the Scheduled Task Handler endpoint requires authentication. Review the code path leading to the col_url function for session checks or access controls
    Affected if The vulnerable endpoint is accessible to authenticated users without additional network or IP restrictions
  5. Confirm network exposure
    Review the application server's outbound network rules and firewall settings. Check if the server can make HTTP requests to arbitrary internal or external addresses
    Affected if The server has outbound network access and no restrictive firewall or network segmentation is in place around the application

You are affected if you run MacCMS version 10.0, the Scheduled Task Handler with the vulnerable col_url function is present and accessible, and the cjurl parameter lacks proper validation while the server maintains outbound network capability.

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 allowlist-based validation for the cjurl parameter to restrict URLs to expected domains/paths only. Additionally, restrict outbound network access from the application server and disable the Scheduled Task Handler if not required.

Fix this in Maccms Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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