dbcve.org
MaccmsApplication

CVE-2025-10397

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 identified in Magicblack MacCMS 2025.1000.4050. This affects an unknown part of the component API Handler. The manipulation of the argument cjurl leads to server-side request forgery. The attack can be initiated remotely. The exploit is publicly available and might 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 · moderate confidence

A Server-Side Request Forgery (SSRF) vulnerability exists in the API Handler component of Magicblack MacCMS 2025.1000.4050. The vulnerability allows remote attackers to manipulate the 'cjurl' parameter to force the server to make arbitrary requests to internal or external resources.

MitigationUpgrade to a patched version of Magicblack MacCMS when available. As an interim control, implement network segmentation and restrict outbound network access from the application server to prevent the exploited requests from reaching sensitive internal services.

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 installation
    Locate the Magicblack MacCMS installation on your server. Check for the presence of MacCMS files in your web root directory, typically identified by common MacCMS file structures such as admin, api, and template folders.
    Affected if Magicblack MacCMS is not present on the server, the vulnerability does not apply.
  2. Verify MacCMS version
    Check the installed version of MacCMS. This is typically found in a version file, admin panel about page, or in a configuration file within the installation directory. Compare your version to the affected version 10.0.
    Affected if The installed version is exactly 10.0, indicating the specific build 2025.1000.4050 is present.
  3. Confirm API Handler component is accessible
    Locate and verify access to the API Handler component endpoint. This is typically found at a path like /api/ or similar endpoint structure within the MacCMS installation. Check if this endpoint is exposed and accessible via HTTP/HTTPS.
    Affected if The API Handler component is not accessible or does not exist in your installation, the attack surface is not present.
  4. Check for cjurl parameter availability
    Examine the API Handler component for the presence of the 'cjurl' parameter. This parameter is used within the API Handler to accept URL inputs for content processing features.
    Affected if The 'cjurl' parameter does not exist in your API Handler implementation, the specific SSRF vector is not present.
  5. Inspect outbound network configuration
    Review server and application configuration for outbound network rules, proxy settings, or firewall policies that control or restrict outgoing requests from the application server.
    Affected if No network restrictions exist on outbound requests from the server, an exploited SSRF could reach arbitrary internal or external resources unrestricted.

You are affected if Magicblack MacCMS version 10.0 is installed, the API Handler component is accessible, and the 'cjurl' parameter is present in the API Handler, allowing potential arbitrary request injection.

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

Upgrade to a patched version of Magicblack MacCMS when available. As an interim control, implement network segmentation and restrict outbound network access from the application server to prevent the exploited requests from reaching sensitive internal services.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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