Skip to content

← Public intelligence

Maven package

org.apache.syncope.client.idrepo:syncope-client-idrepo-common-ui

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 6.8MavenPublished

    Apache Syncope: Reflected XSS on Enduser Login

    CVE-2026-23794 · GHSA-v84m-gfw5-hm2w

    Affected
    • Maven org.apache.syncope.client.idrepo:syncope-client-idrepo-common-ui >= 3.0.0, < 3.0.16; >= 4.0.0, < 4.0.4
    Fixed in
    3.0.164.0.4· Vendor fix available
    Issue
    Reflected XSS in Apache Syncope's Enduser Login page. An attacker that tricks a legitimate user into clicking a malicious link and logging in to Syncope Enduser could steal that user's credentials. This issue affects Apache Syncope: from 3.0 through 3.0.15, from 4.0 through 4.0.3. Users are recommended to upgrade to version 3.0.16 / 4.0.4, which fix this issue.

    Recommended action: Upgrade to 4.0.4 or 3.0.16 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. High, CVSS 7.1MavenPublished

    Apache Syncope Improper Input Validation vulnerability

    CVE-2024-38503 · GHSA-8pxv-x6jq-5vw9

    Affected
    • Maven org.apache.syncope.client.idrepo:syncope-client-idrepo-common-ui >= 2.1.0, < 3.0.8
    Fixed in
    3.0.8· Vendor fix available
    Issue
    When editing a user, group or any object in the Syncope Console, HTML tags could be added to any text field and could lead to potential exploits. The same vulnerability was found in the Syncope Enduser, when editing "Personal Information" or "User Requests". Users are recommended to upgrade to version 3.0.8, which fixes this issue.

    Recommended action: Upgrade to 3.0.8 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →