dbcve.org
IntrexxApplication · Unitedplanet

CVE-2020-24188

MEDIUM · 6.1 CVSS v3.1 Published 2020-10-14
Fix available
A fix is available. Upgrade to 9.4.0 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 the search functionality in Intrexx before 9.4.0 allows remote attackers to inject arbitrary web script or HTML via the request 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 · moderate confidence

Stored XSS vulnerability in Intrexx search functionality allows remote attackers to inject arbitrary JavaScript/HTML through the request parameter before version 9.4.0.

MitigationUpgrade to Intrexx 9.4.0 or later, and implement input validation with proper output encoding on the search 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
IntrexxApplication
Affected:< 9.4.0

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.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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Intrexx installation
    Locate Intrexx installation directory, typically under C:\Program Files\Unitedplanet\Intrexx or /opt/intrexx on Linux systems. Check for intrexx.exe or intrexx service.
    Affected if Intrexx software is present on the system
  2. Identify installed Intrexx version
    Check the version information in the Intrexx installation folder, typically in a version.info file or through the Intrexx administration portal under 'System information' or 'About'. Compare the version number to 9.4.0.
    Affected if Installed version is lower than 9.4.0
  3. Verify search module is enabled
    Access Intrexx administration panel and navigate to 'Module management' or 'Application configuration' to confirm the search functionality module is enabled and accessible to users.
    Affected if Search module is enabled and accessible to end users
  4. Inspect input validation on search parameter
    Review the search parameter configuration in Intrexx administration under 'Input validation' settings, or inspect the XML configuration files in the search module directory for missing or disabled output encoding rules.
    Affected if Input validation is absent, disabled, or does not include output encoding for the search parameter

The environment is affected if Intrexx version is below 9.4.0 AND the search functionality is enabled with inadequate input validation on the search parameter.

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 9.4.0 or later
Fixed in 9.4.0
Interim mitigation

Upgrade to Intrexx 9.4.0 or later, and implement input validation with proper output encoding on the search parameter.

Fix this in Intrexx Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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