CVE-2026-39170
Deferred Deferred - Pending Action
BaseFortify

Publication date: 2026-06-09

Last updated on: 2026-06-09

Assigner: MITRE

Description
SemCms 5.0 is vulnerable to Cross Site Request Forgery (CSRF) via crafted POST request to /admin/semcms_user.php.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-09
Last Modified
2026-06-09
Generated
2026-06-10
AI Q&A
2026-06-09
EPSS Evaluated
N/A
NVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
semcms semcms 5.0
semcms semcms to 5.0 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-352 The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

SEMCMS version 5.0 and earlier contains a Cross-Site Request Forgery (CSRF) vulnerability in the administrative user management module.

The application fails to validate anti-CSRF tokens for user management operations, allowing an authenticated administrator to be tricked into executing unintended actions via a malicious request when visiting an attacker-controlled page.

The affected component is /admin/semcms_user.php, where user creation and modification functions lack CSRF protection.

An attacker can craft a malicious HTML page with an auto-submitting form that performs unauthorized user management actions when visited by an authenticated administrator.

Impact Analysis

Successful exploitation could enable unauthorized account creation, modification of user details, alteration of permissions, or other administrative operations.

This could potentially lead to full application compromise.

Detection Guidance

This vulnerability involves Cross-Site Request Forgery (CSRF) in the /admin/semcms_user.php endpoint of SemCms 5.0. Detection involves monitoring for suspicious POST requests to this endpoint that lack proper anti-CSRF tokens.

You can inspect HTTP traffic to identify POST requests to /admin/semcms_user.php that do not include valid anti-CSRF tokens or originate from unexpected sources.

  • Use tools like curl or wget to simulate POST requests and check server responses for missing CSRF token validation.
  • Example curl command to test the endpoint (replace URL and parameters accordingly):
  • curl -v -X POST https://your-semcms-domain/admin/semcms_user.php -d "username=test&action=create" --cookie "session=your_session_cookie"
  • Use a web proxy or network analyzer (e.g., Burp Suite, Wireshark) to capture and analyze POST requests to /admin/semcms_user.php for missing or invalid CSRF tokens.
Mitigation Strategies

Immediate mitigation steps include implementing anti-CSRF protections on the /admin/semcms_user.php endpoint.

  • Add and validate anti-CSRF tokens for all state-changing POST requests in the administrative user management module.
  • Enforce SameSite cookie attributes to restrict cookie transmission to same-site requests.
  • Verify the origin of requests to ensure they come from trusted sources.
  • Apply strict session management for administrative functions, including session expiration and re-authentication.

Additionally, restrict administrative access to trusted networks or IP addresses where possible until a patch is applied.

Compliance Impact

The Cross-Site Request Forgery (CSRF) vulnerability in SemCms 5.0's administrative user management module can lead to unauthorized user account creation, modification of user details, and alteration of permissions. Such unauthorized administrative actions may result in unauthorized access to sensitive data or system functions.

This lack of proper CSRF protection could compromise the confidentiality and integrity of personal or sensitive data managed by the application, potentially violating data protection requirements under standards like GDPR and HIPAA that mandate strict access controls and protection against unauthorized data manipulation.

Therefore, exploitation of this vulnerability may negatively impact compliance with these regulations by enabling unauthorized administrative actions that could lead to data breaches or improper handling of protected information.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-39170. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart