dbcve.org
S CmsApplication

CVE-2019-9040

HIGH · 8.8 CVSS v3.0 Published 2019-02-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
S-CMS PHP v3.0 has a CSRF vulnerability to add a new admin user via the admin/ajax.php?type=admin&action=add URI, a related issue to CVE-2018-19332.

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 · high confidence

S-CMS PHP v3.0 contains a CSRF vulnerability in admin/ajax.php that allows unauthenticated attackers to trick authenticated administrators into adding new admin user accounts by exploiting the lack of anti-CSRF token validation on the add action.

MitigationImplement synchronizer token pattern (anti-CSRF tokens) on sensitive admin endpoints and validate Origin/Referer headers to prevent cross-site request forgery attacks.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
S CmsApplication
Affected:= 3.0

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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. Verify S-CMS PHP version
    Locate the version file or index page footer that displays the CMS version number
    Affected if The installed version is exactly 3.0 (S-CMS PHP v3.0)
  2. Locate admin/ajax.php file
    Check for the presence of admin/ajax.php in the web root directory
    Affected if The file admin/ajax.php exists in the application installation
  3. Inspect the add action for CSRF token validation
    Open admin/ajax.php and search for code handling the 'add' action (or user creation). Look for anti-CSRF token checks such as isset($_SESSION['token']), csrf_token, or similar validation before processing the add request
    Affected if The add action processes requests without verifying any anti-CSRF token or synchronizer token pattern
  4. Check for Origin/Referer header validation
    Search admin/ajax.php for server-side validation of HTTP Origin or Referer headers before processing admin actions
    Affected if No Origin or Referer header validation is performed on sensitive admin actions like adding users

You are affected if you are running S-CMS PHP v3.0 and the admin/ajax.php file exists with the add action lacking anti-CSRF token checks and Origin/Referer validation.

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 (anti-CSRF tokens) on sensitive admin endpoints and validate Origin/Referer headers to prevent cross-site request forgery attacks.

Fix this in S Cms 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-2019-9040 — 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-2019-9040 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