dbcve.org
Qulog CenterApplication · Qnap

CVE-2025-58469

HIGH · 8.8 CVSS v3.1 Published 2025-11-07
Fix available
A fix is available. Upgrade to 1.8.2.923 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 QuLog 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: QuLog Center 1.8.2.927 ( 2025/09/17 ) 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 · high confidence

This is a cross-site request forgery (CSRF) vulnerability in QuLog Center that allows remote attackers to trick authenticated users into unknowingly executing unwanted actions on the application. By luring a logged-in user to visit a malicious page, attackers can perform operations with the victim's privileges, potentially leading to unauthorized data access or manipulation.

MitigationUpgrade QuLog Center to version 1.8.2.927 or later. Until then, warn users not to click untrusted links while logged into the application.

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
Qulog CenterApplication
Affected:>= 1.8.0.872, < 1.8.2.923

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 if QuLog Center is installed
    Check the QNAP system for QuLog Center application - look in App Center or check for the 'QulogCenter' process running on the system.
    Affected if QuLog Center is installed and running on the system
  2. Determine the installed version of QuLog Center
    Access the QuLog Center web interface and navigate to the About or System Information section to find the exact version number, or check via QNAP CLI using 'qpkg -i | grep -i qulog' if SSH access is available.
    Affected if The version displayed is >= 1.8.0.872 and < 1.8.2.923
  3. Confirm the CSRF protection status (if configurable)
    Examine the QuLog Center security settings within the web interface - look for any CSRF token or anti-CSRF configuration options in the Security or Settings menu.
    Affected if No CSRF token mechanism is enforced for state-changing operations

A system is affected if QuLog Center is installed with a version >= 1.8.0.872 and < 1.8.2.923, where the CSRF vulnerability can be exploited via malicious links 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.8.2.923 or later
Fixed in 1.8.2.923
Interim mitigation

Upgrade QuLog Center to version 1.8.2.927 or later. Until then, warn users not to click untrusted links while logged into the application.

Recommended fix High confidence

QuLog Center 1.8.2.927 or later

  1. 1. Verify current QuLog Center version by accessing the QNAP admin interface and navigating to QuLog Center > Settings > About
  2. 2. If version is >= 1.8.0.872 and < 1.8.2.923, the system is vulnerable
  3. 3. Download QuLog Center version 1.8.2.927 or later from the official QNAP download center at www.qnap.com
  4. 4. In the QNAP admin interface, go to QuLog Center > Settings > Backup/Restore
  5. 5. Create a backup of current QuLog Center configuration settings
  6. 6. Apply the firmware update containing the QuLog Center fix through App Center or the standard QNAP firmware update mechanism
  7. 7. After upgrade, verify the new version is 1.8.2.927 or later
  8. 8. Confirm the vulnerability is resolved by reviewing the QuLog Center release notes
Caveat Standard QNAP firmware/app update risks apply - ensure configuration backup before upgrading

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

Fix this in Qulog Center Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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