dbcve.org
ContactsApplication · Synology

CVE-2025-13167

MEDIUM · 5.4 CVSS v3.1 Published 2026-05-27
Fix available
A fix is available. Upgrade to 1.0.10-20659 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
Improper neutralization of input during web page generation ('Cross-site Scripting') vulnerability in contact functionality in Synology Contacts before 1.0.10-20659 allows remote authenticated users to read or write specific files containing non-sensitive information via unspecified vectors.

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

Cross-site Scripting (XSS) vulnerability in the contact functionality of Synology Contacts allows remote authenticated users to inject malicious scripts via unspecified vectors in the web page generation process, potentially enabling unauthorized file read/write operations on specific non-sensitive files.

MitigationUpgrade Synology Contacts to version 1.0.10-20659 or later to patch the XSS vulnerability. Review and validate contact functionality inputs after upgrade.

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
ContactsApplication
Affected:< 1.0.10-20659

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. Verify Synology Contacts package is installed
    Access Synology DSM > Package Center and look for Synology Contacts in the installed package list, or run command: cat /var/packages/SynologyContacts/INFO 2>/dev/null
    Affected if Package is not installed or the INFO file does not exist - not affected. If installed, continue to version check.
  2. Identify the installed version of Synology Contacts
    In Package Center, click on Synology Contacts and view the version number displayed. Or via command line: cat /var/packages/SynologyContacts/INFO | grep version
    Affected if The displayed version is less than 1.0.10-20659 - affected by the vulnerability.
  3. Confirm contact functionality is accessible
    Verify the Synology Contacts package is not disabled and the web interface is accessible via DSM > Main Menu > Contacts, or check that the package status shows as Running
    Affected if The contact functionality is running and accessible to authenticated users - the XSS attack surface exists.
  4. Compare version against affected range
    If version is shown as 1.0.10-20659 or higher, the vulnerability is patched. If version shows any version below 1.0.10-20659 (e.g., 1.0.9-xxxxx), the environment falls within the affected range
    Affected if Installed version is below 1.0.10-20659 - the environment is affected and should be investigated.

You are affected if Synology Contacts is installed with a version number lower than 1.0.10-20659 and the contact functionality is accessible to authenticated users.

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

Upgrade Synology Contacts to version 1.0.10-20659 or later to patch the XSS vulnerability. Review and validate contact functionality inputs after upgrade.

Recommended fix High confidence

1.0.10-20659 or later

  1. 1. Log in to your Synology DSM (DiskStation Manager) as an administrator
  2. 2. Open the Package Center from the main menu
  3. 3. Search for 'Synology Contacts' in the package list
  4. 4. If an update is available, click on 'Update' next to Synology Contacts
  5. 5. Confirm the update to version 1.0.10-20659 or later
  6. 6. Wait for the update to complete and verify the new version is installed

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

Fix this in Contacts Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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