CVE-2020-4775
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 cross-site scripting (XSS) vulnerability may impact IBM Curam Social Program Management 7.0.9 and 7.0.10. This vulnerability allows attackers to inject malicious scripts into web applications for the purpose of running unwanted actions on the end user's device, restricted to a single location. IBM X-Force ID: 189153.
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 confidenceA cross-site scripting (XSS) vulnerability in IBM Curam Social Program Management versions 7.0.9 and 7.0.10 allows attackers to inject malicious scripts into web applications. The attack is restricted to a single location, meaning the injected script affects a specific input field or page area.
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= 7.0.9.0= 7.0.10.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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Verify IBM Curam SPM versionAccess the IBM Curam Social Program Management administration console or check the installation directory for version information. Common locations include the about page in the admin UI or version.properties file in the installation root.Affected if The installed version matches exactly 7.0.9.0 or 7.0.10.0 (these are the only affected versions listed)
-
Confirm web interface is accessibleDetermine if the IBM Curam web application is exposed by checking the application server configuration (such as WebSphere or similar) and verifying the Curam application is deployed and running.Affected if The web interface is enabled and accessible to users or attackers on the network
-
Identify exposed input fieldsReview the IBM Curam web application endpoints, particularly forms that accept user input in the affected module. Check the application's URL structure and available servlets or JSP pages.Affected if User-facing input forms or parameters are present in the web interface without proper input validation or output encoding
-
Check for existing input validationInspect the application's configuration files or web.xml for any existing input validation filters, or review the application's source code (if accessible) for sanitization functions applied to user inputs.Affected if No input validation or output encoding is implemented on the affected input points, making script injection possible
A user is affected if they have IBM Curam Social Program Management version 7.0.9.0 or 7.0.10.0 deployed with an accessible web interface that lacks proper input validation on the vulnerable input field.
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 the vendor patch or upgrade to a fixed version. Until then, implement output encoding and input validation on affected input points to mitigate script injection.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-4775 — 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-4775 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