dbcve.org
SemcmsApplication · Sem Cms

CVE-2018-18783

MEDIUM · 6.1 CVSS v3.0 Published 2018-10-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
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
XSS was discovered in SEMCMS V3.4 via the semcms_remail.php?type=ok umail parameter.

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

Reflected Cross-Site Scripting (XSS) vulnerability in SEMCMS V3.4 where the 'umail' parameter in semcms_remail.php is not properly sanitized, allowing injection of malicious JavaScript through the URL.

MitigationImplement proper input validation and output encoding for the umail parameter in semcms_remail.php to prevent XSS injection.

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
SemcmsApplication
Affected:= 3.4

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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 exists
    Locate SEMCMS files in the web server document root, typically found in directories like /var/www/html/, /www/html/, or C:\inetpub\wwwroot\. Look for SEMCMS-specific files and folders.
    Affected if SEMCMS files are present on the server
  2. Identify SEMCMS version
    Check for a version file or footer in the application. Common locations include a version.php file, CHANGELOG.txt, or the main index page source. The affected version is 3.4.
    Affected if The installed version is exactly 3.4
  3. Locate the vulnerable script
    Search for the file semcms_remail.php in the web root directories. This file handles password reset or email reminder functionality.
    Affected if The file semcms_remail.php exists in the installation
  4. Test the vulnerable parameter
    Access the URL endpoint that contains semcms_remail.php with the umail parameter, such as: http://[target]/[email protected]. Observe if the value is reflected back in the response without sanitization.
    Affected if The umail parameter value is reflected in the HTML response without encoding or sanitization

The environment is affected if SEMCMS version 3.4 is installed and the semcms_remail.php file is accessible, allowing the umail parameter to reflect unescaped input in the response.

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 proper input validation and output encoding for the umail parameter in semcms_remail.php to prevent XSS injection.

Fix this in Semcms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-18783 — 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-2018-18783 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