LiveActive security incident?Get immediate response
CVE Record

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

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.

MediumCVSS 6.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2018-25200 affects Zsoft OOP CMS BLOG 1.0. The reported flaw can allow creation of administrator accounts through the user-addition function, creating a path to unauthorized site control. Treat exposed installations as business-relevant, especially if the CMS manages public content or customer-facing pages.

Executive priority

Prioritize discovery and containment over broad emergency response. If the product is internet-facing or business-critical, act quickly because unauthorized administrator creation could lead to site takeover or content manipulation.

Technical view

The issue is a CWE-352 cross-site request forgery in OOP CMS BLOG 1.0 involving addUser.php. Public reporting says crafted POST requests can create administrative users. The CVSS 4.0 score is 6.9, with network attack vector and low complexity. No vendor patch information is included in the provided sources.

Likely exposure

Exposure is limited to organizations running Zsoft OOP CMS BLOG version 1.0, particularly if the administrative or user-management functions are reachable from the internet.

Exploitation context

Exploit-DB is listed as a public exploit reference, so proof-of-concept information appears publicly available. The source bundle says this CVE is not in CISA KEV, and no cited source confirms active exploitation.

Researcher notes

Evidence supports OOP CMS BLOG 1.0 only. Sources name addUser.php and administrative account creation, but do not provide vendor remediation details. Avoid assuming other versions or products are affected without additional confirmation.

Mitigation direction

  • Identify any OOP CMS BLOG 1.0 deployments.
  • Check vendor or project guidance for updates or security fixes.
  • Restrict access to administrative and user-management paths.
  • Disable or retire exposed instances if no maintained fix exists.
  • Review and remove unauthorized administrator accounts.

Validation and detection

  • Confirm product name and version on all CMS hosts.
  • Review account lists for unexpected administrative users.
  • Check web logs for suspicious add-user activity.
  • Verify administrative paths are not publicly reachable.
  • Document compensating controls if no patch is available.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-25200 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.9 (4.0)
Known Exploited
No
Published

Vector: 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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.9CVSS 4.0MediumCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:LPrimary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

6.9Medium
CVSS 4.0 vector shape for CVE-2018-25200Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: 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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ZsoftOOP CMS BLOG1.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.