dbcve.org
Notification CenterApplication · Qnap

CVE-2025-58468

HIGH · 8.8 CVSS v3.1 Published 2026-06-10
Fix available
A fix is available. Upgrade to 1.10.0.3291 or later.
See remediation →
95/100
Remediation priority · Urgent
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
A cross-site request forgery (CSRF) vulnerability has been reported to affect Notification Center. The remote attackers can then exploit the vulnerability to gain privileges or hijack user identities. We have already fixed the vulnerability in the following version: Notification Center 1.10.0.3291 and later

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

This is a cross-site request forgery (CSRF) vulnerability in Notification Center. Attackers can craft malicious requests that trick authenticated users into performing unintended actions, potentially allowing privilege escalation or user identity hijacking. The vulnerability exploits the lack of proper CSRF token validation in the application.

MitigationUpgrade to Notification Center version 1.10.0.3291 or later, which contains the fix for this CSRF vulnerability. If immediate upgrading is not possible, implement anti-CSRF tokens and SameSite cookie attributes as a compensating control.

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
Notification CenterApplication
Affected:>= 1.10.0, < 1.10.0.3291

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 the Notification Center application
    Locate the Notification Center software on your system. Check the application name, installed software list, or service details to confirm the product name matches 'Notification Center'
    Affected if The application is named Notification Center or a variant thereof
  2. Find the installed version
    Access the application's 'About' section, check the installation directory for a version file, or use system commands to query the installed software version (e.g., 'Get-ItemProperty' in Windows, RPM query on Linux, or checking the application's runtime information)
    Affected if The version returned is lower than 1.10.0.3291 or cannot be determined to be 1.10.0.3291 or higher
  3. Verify CSRF protection is enabled
    Inspect the application's configuration files or settings panel for CSRF protection options. Look for settings related to 'CSRF token validation', 'request verification', or 'origin validation' in the Notification Center admin or configuration interface
    Affected if CSRF protection is disabled, missing, or not configurable in the application
  4. Check for security tokens in POST requests
    Use a web proxy or browser developer tools to capture a POST request from the Notification Center. Examine whether the request includes a security token, anti-CSRF token, or CSRF header such as 'X-CSRF-Token' or 'X-XSRF-Token'
    Affected if POST requests to Notification Center do not include any security token or the token is missing from sensitive actions

You are affected if Notification Center is installed and the version is below 1.10.0.3291 OR if CSRF token validation is not implemented in the application.

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.10.0.3291 or later
Fixed in 1.10.0.3291
Interim mitigation

Upgrade to Notification Center version 1.10.0.3291 or later, which contains the fix for this CSRF vulnerability. If immediate upgrading is not possible, implement anti-CSRF tokens and SameSite cookie attributes as a compensating control.

Recommended fix Moderate confidence

Notification Center 1.10.0.3291

  1. 1. Log in to your QNAP NAS as an administrator.
  2. 2. Navigate to Notification Center in the QNAP interface.
  3. 3. Check the current version of Notification Center.
  4. 4. If the installed version is earlier than 1.10.0.3291, update Notification Center to version 1.10.0.3291 or later.
  5. 5. Verify the update was successful by checking the version number after the update completes.

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

Fix this in Notification Center Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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