dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2026-39170

MEDIUM · 6.3 CVSS v3.1 Published 2026-06-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
SemCms 5.0 is vulnerable to Cross Site Request Forgery (CSRF) via crafted POST request to /admin/semcms_user.php.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

SemCms 5.0 lacks anti-CSRF protections on the admin user management page (semcms_user.php). Attackers can trick authenticated administrators into submitting malicious POST requests to create, modify, or delete user accounts by luring them to a crafted webpage, exploiting the application's trust in the authenticated user's browser.

MitigationImplement synchronizer token pattern with unique CSRF tokens on all state-changing forms and validate them server-side; additionally enable SameSite cookie attributes and validate Origin/Referer headers as defense-in-depth.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm SemCms installation and version
    Locate the SemCms installation directory and check version identifiers in the main index file, about page, or version metadata files. Compare the installed version to the affected version SemCms 5.0.
    Affected if The installed version is SemCms 5.0 exactly.
  2. Verify the vulnerable endpoint exists
    Check if the file /admin/semcms_user.php exists in the web root or admin directory of the SemCms installation.
    Affected if The /admin/semcms_user.php endpoint is present and accessible.
  3. Inspect the endpoint for anti-CSRF token presence
    Open /admin/semcms_user.php in a text editor or fetch it via HTTP and examine the HTML forms for the presence of a CSRF token parameter (such as a hidden input field with a random value or a token in the form action).
    Affected if The forms in /admin/semcms_user.php do not contain any anti-CSRF token fields.
  4. Check SameSite cookie configuration
    Examine the application source code or session configuration for cookie creation calls and verify if SameSite attribute is set to Strict or Lax on session or authentication cookies.
    Affected if Cookies are missing SameSite=Strict or SameSite=Lax attributes.

A user is affected if running SemCms 5.0 with the /admin/semcms_user.php endpoint accessible and lacking anti-CSRF token protection on state-changing operations.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement synchronizer token pattern with unique CSRF tokens on all state-changing forms and validate them server-side; additionally enable SameSite cookie attributes and validate Origin/Referer headers as defense-in-depth.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-39170 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-39170 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data