# CVE-2018-25200: OOP CMS BLOG 1.0 Cross-Site Request Forgery via addUser.php

> Unauthenticated attackers can create administrative accounts via CSRF in OOP CMS BLOG, leading to full system compromise.

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

## What is CVE-2018-25200?

CVE-2018-25200 is a medium-severity vulnerability in Zsoft OOP CMS BLOG, published on 6 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OOP CMS BLOG 1.0 contains a cross-site request forgery vulnerability that allows unauthenticated attackers to create administrative user accounts by crafting malicious POST requests. Attackers can submit forms to the addUser.php endpoint with parameters including userName, password, email, and role set to administrative privileges to gain unauthorized access.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2018-25200?

It affects 1 product.


Products: Tomalofficial Php Oop Cms Blog.

## How do I fix CVE-2018-25200?

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

## Is CVE-2018-25200 being exploited?

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

## Other vulnerabilities in Zsoft OOP CMS BLOG

- [CVE-2018-25199](https://insights.sbomify.com/CVE-2018-25199/): OOP CMS BLOG 1.0 SQL Injection via search parameter (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-25200 and fix it if it is affected.

What it is: CVE-2018-25200 is a medium-severity vulnerability in Zsoft OOP CMS BLOG, published on 6 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-2018-25200 exists.

Affected product: Zsoft OOP CMS BLOG. 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-2018-25200/ (Markdown: https://insights.sbomify.com/CVE-2018-25200/index.md)
```

## Sources

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

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