# CVE-2026-4953: mingSoft MCMS Editor Endpoint BaseAction.java catchImage server-side request forgery

> Remote attackers can exploit a server-side request forgery vulnerability in the mingSoft MCMS editor endpoint to access internal resources.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Mar 2026
- **Updated:** 30 Mar 2026
- **Also known as:** GHSA-xmm3-9x39-98r5

## What is CVE-2026-4953?

CVE-2026-4953 is a medium-severity server-side request forgery vulnerability in mingSoft MCMS, published on 27 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A weakness has been identified in mingSoft MCMS up to 5.5.0. This issue affects the function catchImage of the file net/mingsoft/cms/action/BaseAction.java of the component Editor Endpoint. Executing a manipulation of the argument catchimage can lead to server-side request forgery. It is possible to launch the attack remotely. The exploit has been made available to the public and could be used for attacks.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-4953?


## How do I fix CVE-2026-4953?

No fix has been published for CVE-2026-4953 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-4953 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-4953 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-4953 and fix it if it is affected.

What it is: CVE-2026-4953 is a medium-severity server-side request forgery vulnerability in mingSoft MCMS, published on 27 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-4953 exists.

Affected product: mingSoft MCMS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-4953/ (Markdown: https://insights.sbomify.com/CVE-2026-4953/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-4953
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-4953
- OSV: https://osv.dev/vulnerability/CVE-2026-4953

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-4953/
Summaries are generated and may contain mistakes; the official description above is the record.