dbcve.org
SeeddmsApplication

CVE-2018-12943

MEDIUM · 6.1 CVSS v3.0 Published 2018-07-31
Fix available
A fix is available. Upgrade to 5.1.8 or later.
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
Cross-Site Scripting (XSS) vulnerability in every page that includes the "action" URL parameter in SeedDMS (formerly LetoDMS and MyDMS) before 5.1.8 allows remote attackers to inject arbitrary web script or HTML via the action 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 · high confidence

Reflected XSS vulnerability in SeedDMS where the 'action' URL parameter is not properly sanitized before being reflected in page output, allowing injection of arbitrary JavaScript/HTML.

MitigationUpgrade to SeedDMS version 5.1.8 or later which contains the fix; alternatively, implement proper input validation and output encoding on the action parameter.

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
SeeddmsApplication
Affected:< 5.1.8

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. Identify SeedDMS installation version
    Locate the version file or version constant within the SeedDMS installation directory (commonly found in version.php, config.php, or the main index file). Read the version number defined there.
    Affected if The installed version is lower than 5.1.8 (for example, 5.1.7, 5.1.6, or earlier)
  2. Confirm web interface is exposed
    Determine if the SeedDMS web interface is accessible over HTTP/HTTPS to users or attackers. This is typically served from the document root or a subdirectory where SeedDMS is installed.
    Affected if The web interface is publicly or internally accessible without additional authentication barriers
  3. Locate the 'action' parameter handler
    Inspect the PHP files that handle the 'action' URL parameter, typically in the main entry point or controller files (such as index.php or a routing file). Look for code that retrieves the 'action' parameter via $_GET['action'] or similar.
    Affected if The code reads the 'action' parameter without sanitization before using it in page output
  4. Verify lack of output encoding on the action parameter
    Search the codebase for functions that perform output encoding (such as htmlspecialchars, htmlentities, or a templating engine's auto-escaping) applied to the 'action' value before it is echoed into HTML.
    Affected if No output encoding function is applied to the 'action' parameter before it is reflected in the response
  5. Test for reflected XSS in the action parameter
    Submit a request to the SeedDMS interface with a crafted 'action' parameter containing a test payload (for example, action=<script>alert(1)</script> or action=\" onfocus=\"alert(1)\" autofocus=\"). Examine the HTTP response to see if the payload is rendered as literal HTML/JS instead of being escaped.
    Affected if The payload is reflected unchanged in the HTML response and the browser executes the injected JavaScript

A user is affected if SeedDMS version is below 5.1.8 AND the web interface is accessible AND the 'action' parameter is handled without output encoding, allowing injected scripts to execute in a user's browser.

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
Upgrade available Upgrade to 5.1.8 or later
Fixed in 5.1.8
Interim mitigation

Upgrade to SeedDMS version 5.1.8 or later which contains the fix; alternatively, implement proper input validation and output encoding on the action parameter.

Fix this in Seeddms Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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