IntrexxApplication

CVE-2025-47201

MEDIUM · 5.4 CVSS v3.1 Published 2025-05-02
Fix available
A fix is available. Upgrade to 12.0.4 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
In Intrexx Portal Server before 12.0.4, multiple Velocity-Scripts are susceptible to the execution of unrequested JavaScript code in HTML, aka XSS.

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

Intrexx Portal Server versions before 12.0.4 contain multiple vulnerable Velocity templates that fail to properly sanitize user-controlled input before rendering it in HTML. This allows attackers to inject malicious JavaScript code that executes in the context of other users' browsers, enabling session hijacking, credential theft, or defacement.

MitigationUpgrade to Intrexx Portal Server version 12.0.4 or later. Until a patch is available, implement output encoding in Velocity scripts and deploy WAF rules to detect and block XSS payloads.

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:< 12.0.4

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

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

  1. Identify Intrexx Portal Server version
    Check the installed version of Intrexx Portal Server. This is typically visible in the administration interface under 'System Information' or can be found in the product'sAbout dialog. The version may also be logged in installation logs or the application startup logs.
    Affected if The installed version is lower than 12.0.4 (e.g., 12.0.3, 12.0.2, 11.x, etc.)
  2. Confirm the product is Intrexx Portal Server
    Verify that the affected application is specifically Intrexx Portal Server and not another Intrexx product. Check the product name in the installation directory or administration console.
    Affected if The product is Intrexx Portal Server and the version is below 12.0.4
  3. Identify Velocity template usage
    Locate Velocity template files (.vm files) in the Intrexx installation directory, particularly in custom modules or handlers that process user-provided input. These are commonly found in the 'velocity' or 'templates' subdirectories within the web application folder.
    Affected if Custom or modified Velocity templates exist that render user input without output encoding

You are affected if Intrexx Portal Server is installed and its version is below 12.0.4, as the vulnerable Velocity templates exist in all prior versions.

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.

dbcve · scoped
Upgrade available Upgrade to 12.0.4 or later
Fixed in 12.0.4
Interim mitigation

Upgrade to Intrexx Portal Server version 12.0.4 or later. Until a patch is available, implement output encoding in Velocity scripts and deploy WAF rules to detect and block XSS payloads.

Recommended fix High confidence

Intrexx Portal Server 12.0.4

  1. Verify current Intrexx Portal Server version by checking the administration interface or installation directory
  2. Review Intrexx upgrade documentation for version 12.0.4 at security.intrexx.com
  3. Create a complete backup of the current Intrexx installation including database and configuration files
  4. Test the upgrade in a non-production environment before applying to production
  5. Apply the upgrade to version 12.0.4 following Intrexx official upgrade procedures
  6. Verify the installation was successful and all services started properly
  7. Validate that the XSS vulnerability is remediated by testing the previously vulnerable Velocity-scripts

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Intrexx Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-47201 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-47201 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