CVE-2019-11643
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 · uneditedPersistent XSS has been found in the OneShield Policy (Dragon Core) framework before 5.1.10. Remote adversaries can inject malicious JavaScript into textboxes decorated with type string, which is subsequently stored to the applicable data store. This can be exploited remotely by both authenticated and unauthenticated users.
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 persistent XSS vulnerability exists in OneShield Policy Dragon Core framework versions prior to 5.1.10. Attackers can inject malicious JavaScript into textbox fields decorated with type string, which gets stored in the database and executes when other users view the affected data. Both authenticated and unauthenticated users can exploit this vulnerability.
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.10CVSS 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 the installed OneShield Policy versionLocate the version information for OneShield Policy Dragon Core framework - typically found in application configuration files, about pages, or system information panels within the OneShield applicationAffected if The installed version is any version prior to 5.1.10
-
Compare your version to the affected rangeDocument the exact version number and verify it falls below 5.1.10Affected if Version is less than 5.1.10
-
Examine textbox field configurationsReview the application forms and templates for textbox fields decorated with type string attribute, particularly in data entry forms that accept user inputAffected if The application uses textbox fields with type string that accept user-supplied input without validation
-
Inspect database storage for suspicious contentQuery the database tables that store form input from textbox fields - look for HTML script tags, JavaScript event handlers, or encoded script payloads in text columnsAffected if The database contains any stored scripts or malicious payloads in text fields that could execute when viewed by other users
-
Review application output for unencoded dataAccess the application as a user would and examine how textbox field data is displayed back - check if user-supplied text renders as raw HTML or is properly encodedAffected if User input from textbox fields is rendered without output encoding, allowing script execution
You are affected if your OneShield Policy version is below 5.1.10 and the application uses textbox fields with type string that accept user input, as the stored XSS can execute when other users view the data.
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 data5.1.10
Upgrade to OneShield Policy Dragon Core framework version 5.1.10 or later. Additionally, implement output encoding for all user-supplied data displayed in the application and sanitize existing data in the database that may contain malicious scripts.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11643 — 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-11643 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