CVE-2018-25200: OOP CMS BLOG 1.0 contains a cross-site request forgery vulnerability that allows unauthenticated attackers to

This week

MEDIUM 5.3REMOTEDOWNGRADE

CVE-2018-25200 is a medium-severity flaw (CVSS 5.3) affecting php oop cms blog. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Public exploit reference
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	5.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.2% (top 95%)
CISA exploited list	No
Weakness	CWE-352
Published	2026-03-06
Last modified	2026-06-17

Publisher (CNA): VulnCheck · Vendor: tomalofficial

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-03-06 13:16 UTCPublished CVE record published
2026-06-17 01:54 UTCUpdated Record last modified

tomalofficial php oop cms blog DOWNGRADE

Affected: 1.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.0

1. Check installed version

apt-cache policy php-oop-cms-blog || rpm -q php-oop-cms-blog || php-oop-cms-blog --version

2. No fixed release: DOWNGRADE to a release before 1.0 (Debian / Ubuntu)

apt-cache madison php-oop-cms-blog sudo apt install php-oop-cms-blog=<VERSION_BEFORE_1.0> sudo apt-mark hold php-oop-cms-blog

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list php-oop-cms-blog sudo dnf downgrade php-oop-cms-blog-<VERSION_BEFORE_1.0> sudo dnf versionlock add php-oop-cms-blog

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2018-25200?

php oop cms blog: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2018-25200 being exploited?

CVE-2018-25200 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2018-25200 affect?

CVE-2018-25200 affects php oop cms blog. Severity is medium (CVSS 5.3). 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 wi

How urgent is CVE-2018-25200?

Priority 30/100. Public exploit reference; Remotely exploitable, no login, no user action

Software pages

PHP vulnerabilities

Related CVEs

CVE-2018-25199 HIGH 8.2 DOWNGRADE OOP CMS BLOG 1.0 contains SQL injection vulnerabilities that allow unauthenticated attackers to execute arbitr

References

← Back to latest CVEs