CVE-2019-12932
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 · uneditedA stored XSS vulnerability was found in SeedDMS 5.1.11 due to poorly escaping the search result in the autocomplete search form placed in the header of out/out.Viewfolder.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 · high confidenceA stored cross-site scripting (XSS) vulnerability exists in SeedDMS 5.1.11 where the autocomplete search form in the header of out/out.Viewfolder.php fails to properly escape search results. When users perform searches, malicious scripts stored in the search index can be executed in their browsers.
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= 5.1.11CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify SeedDMS installed versionCheck the version.php file or any version indicator in the SeedDMS installation directory (commonly found in the root or in a config file). Look for a version number displayed in the application footer or in the admin panel.Affected if The installed version is exactly 5.1.11
-
Confirm the vulnerable file existsLocate the file out/out.Viewfolder.php in the web root directory. Verify its presence and check the file for autocomplete search form handling code.Affected if The file out/out.Viewfolder.php exists and contains search/ autocomplete functionality
-
Check for unescaped search output codeInspect the out/out.Viewfolder.php file around the autocomplete search form section. Look for code that renders search results without using HTML encoding functions (such as htmlspecialchars or equivalent escaping).Affected if The code displays search results in the autocomplete field without proper output encoding
-
Determine if search feature is accessibleAttempt to access the SeedDMS web interface and perform a search using the autocomplete search form in the header. Verify the search functionality returns results.Affected if The autocomplete search feature is enabled and returns results from the search index
A user is affected if they are running SeedDMS version 5.1.11 with the autocomplete search feature in out/out.Viewfolder.php enabled, where search results are rendered without HTML encoding.
Generated from the published advisory. Verify against your own configuration.
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 dataApply proper output encoding/escaping to all search result data before rendering it in the autocomplete field in out/out.Viewfolder.php, using context-aware encoding functions appropriate for HTML output.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12932 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-12932 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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