CVE-2020-13639
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 discovered in the ECT Provider in OutSystems before 2020-09-04, affecting generated applications. It could allow an unauthenticated remote attacker to craft and store malicious Feedback content into /ECT_Provider/, such that when the content is viewed (it can only be viewed by Administrators), attacker-controlled JavaScript will execute in the security context of an administrator's browser. This is fixed in Outsystems 10.0.1005.2, Outsystems 11.9.0 Platform Server, and Outsystems 11.7.0 LifeTime Management Console.
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 XSS vulnerability exists in the ECT Provider component of OutSystems. An unauthenticated remote attacker can inject malicious JavaScript into Feedback content submitted to the /ECT_Provider/ endpoint. When administrators view this stored content in their browser, the attacker-controlled JavaScript executes within the administrator's security context.
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>= 11, < 11.7.0>= 10, < 10.0.1005.2>= 11, < 11.9.0CVSS 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.1/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 installed OutSystems platform versionCheck the Platform Server or LifeTime Management Console version through the OutSystems Administration Console, Service Center, or LifeTime console. This is typically found under 'Platform Administration' or 'Server Management' interfaces.Affected if The installed version falls within >= 11, < 11.9.0 for Platform Server; >= 11, < 11.7.0 for LifeTime; or >= 10, < 10.0.1005.2 for OutSystems 10 releases.
-
Confirm ECT Provider component is installedReview the installed modules or components in the OutSystems environment through the Service Center or LifeTime console. Look for 'ECT Provider' or 'External Content Type Provider' in the module/component list.Affected if The ECT Provider component is present and installed in the environment.
-
Verify /ECT_Provider/ endpoint is accessibleAttempt to access the /ECT_Provider/ endpoint from a browser or HTTP client (e.g., curl https://<hostname>/ECT_Provider/). Check if the endpoint responds and accepts input.Affected if The /ECT_Provider/ endpoint is reachable and does not require authentication for initial access.
-
Inspect Feedback submission functionalityLocate the Feedback form or input mechanism associated with the ECT Provider. This is typically found in user-facing interfaces where feedback content can be submitted.Affected if The Feedback submission allows unauthenticated input and stores it for later display to administrators.
If the installed OutSystems version is below 11.9.0 (Platform Server), 11.7.0 (LifeTime), or 10.0.1005.2 (OutSystems 10), AND the ECT Provider component is installed with the /ECT_Provider/ endpoint exposed to untrusted users, the environment is affected by this stored XSS vulnerability.
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.
dbcve · scoped10.0.1005.211.7.011.9.0
Upgrade OutSystems platform to version 10.0.1005.2, 11.9.0, or 11.7.0 (LifeTime) as appropriate. Until patched, restrict access to the /ECT_Provider/ endpoint from untrusted networks.
OutSystems 10.0.1005.2 (Platform Server), OutSystems 11.9.0 (Platform Server), or OutSystems 11.7.0 (LifeTime Management Console)
- 1. Identify the currently installed OutSystems component(s): Platform Server, LifeTime Management Console, or both
- 2. For OutSystems Platform Server 10.x: Upgrade to version 10.0.1005.2 or later
- 3. For OutSystems Platform Server 11.x: Upgrade to version 11.9.0 or later
- 4. For OutSystems LifeTime Management Console 11.x: Upgrade to version 11.7.0 or later
- 5. After upgrading, verify the ECT Provider module has been updated and test the /ECT_Provider/ functionality
- 6. Confirm the XSS vulnerability is remediated by attempting to inject test script content and verifying it is properly escaped
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-13639 — 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-2020-13639 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