CVE-2025-23363
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 vulnerability has been identified in Teamcenter V14.1 (All versions), Teamcenter V14.2 (All versions), Teamcenter V14.3 (All versions < V14.3.0.14), Teamcenter V2312 (All versions < V2312.0010), Teamcenter V2406 (All versions < V2406.0008), Teamcenter V2412 (All versions < V2412.0004). The SSO login service of affected applications accepts user-controlled input that could specify a link to an external site. This could allow an attacker to redirect the legitimate user to an attacker-chosen URL to steal valid session data. For a successful exploit, the legitimate user must actively click on an attacker-crafted link.
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 confidenceOpen redirect vulnerability in Teamcenter's SSO login service. The service accepts user-controlled input (likely via a redirect parameter) that specifies an external URL, allowing attackers to craft malicious links that redirect legitimate authenticated users to attacker-controlled domains to steal session cookies or credentials.
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>= 14.3, < 14.3.0.14>= 2312.0, < 2312.0010>= 2406.0, < 2406.0008>= 2412.0, < 2412.0004= 14.1= 14.2CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/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 Teamcenter versionLocate the Teamcenter installation directory and check the version information file, typically found in the installation logs or registry entries. Common locations include the TC_ROOT directory or the installer logs. Alternatively, access the Teamcenter About dialog from the application or check the version via the System Administration utilities.Affected if The installed version falls within any of these ranges: 14.1, 14.2, >= 14.3 but < 14.3.0.14, >= 2312.0 but < 2312.0010, >= 2406.0 but < 2406.0008, >= 2412.0 but < 2412.0004.
-
Verify SSO login service is enabledAccess the Teamcenter System Administration or Configuration Manager and inspect the SSO/SSO login configuration settings. Check if Single Sign-On authentication is configured and active for the Teamcenter deployment.Affected if SSO login is enabled and configured as the authentication mechanism.
-
Inspect SSO redirect parameter configurationReview the SSO configuration files (typically in the TC_DATA directory or within the SSO provider configuration) for the redirect or return URL parameter handling. Look for settings controlling where users are redirected after authentication.Affected if The SSO configuration allows external/unvalidated URLs in the redirect parameter without strict domain allowlist enforcement.
-
Check URL validation settings for SSO redirectsExamine the SSO security settings or custom configuration files for any URL validation, allowlist, or domain restriction rules applied to the redirect parameter. Look for patterns like allowed domains, whitelist entries, or validation logic.Affected if No strict URL validation or allowlist is configured for the redirect parameter, or external domains are explicitly permitted.
-
Review authentication logs for suspicious redirect patternsSearch Teamcenter or web server logs (IIS, Apache, or the SSO provider logs) for authentication events with unusual redirect URLs. Look for redirects to unfamiliar or external domains during login sequences.Affected if Log entries show redirects to non-internal or unrecognized domains following SSO authentication attempts.
A user is affected if their Teamcenter version is in the vulnerable ranges AND SSO login is enabled without strict URL validation on the redirect parameter, allowing external domains to be specified as redirect targets.
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 · scoped14.3.0.142312.00102406.0008
Apply vendor patches to reach minimum fixed versions (V14.3.0.14, V2312.0010, V2406.0008, V2412.0004). As an interim control, implement strict URL validation or allowlist enforcement on the SSO login redirect parameter to prevent external domain redirection.
Upgrade to the version specific to your release line: V14.3.0.14 (for 14.3.x), V2312.0010 (for 2312.x), V2406.0008 (for 2406.x), or V2412.0004 (for 2412.x)
- 1. Identify the current Teamcenter version by checking the installed version in the Teamcenter Administration or system information.
- 2. If running Teamcenter V14.3.x, upgrade to V14.3.0.14 or later.
- 3. If running Teamcenter V2312.x, upgrade to V2312.0010 or later.
- 4. If running Teamcenter V2406.x, upgrade to V2406.0008 or later.
- 5. If running Teamcenter V2412.x, upgrade to V2412.0004 or later.
- 6. After upgrading, verify the SSO login service no longer accepts unvalidated external URL parameters by testing with a crafted redirect URL.
- 7. Confirm the application functions normally post-upgrade.
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-2025-23363 — 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-2025-23363 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