dbcve.org
QcalagentApplication · Qnap

CVE-2021-38677

MEDIUM · 6.1 CVSS v3.1 Published 2022-01-14
Fix available
A fix is available. Upgrade to 1.1.7 or later.
See remediation →
68/100
Remediation priority · Elevated
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 scripting (XSS) vulnerability has been reported to affect QNAP device running QcalAgent. If exploited, this vulnerability allows remote attackers to inject malicious code. We have already fixed this vulnerability in the following versions of QcalAgent: QcalAgent 1.1.7 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

A cross-site scripting (XSS) vulnerability in QcalAgent running on QNAP devices allows remote attackers to inject malicious code through the application, potentially compromising user sessions or executing arbitrary scripts in the context of the affected application.

MitigationUpdate QcalAgent to version 1.1.7 or later to remediate the vulnerability.

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
QcalagentApplication
Affected:< 1.1.7

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Locate QcalAgent on the QNAP device
    Access the QNAP device via SSH or QNAP GUI. Check installed applications through the App Center or list installed packages using CLI tools like 'qpkg --list' or by inspecting /share/HDA_DATA/.qpkg/ for the QcalAgent directory.
    Affected if QcalAgent is installed on the device
  2. Determine the installed QcalAgent version
    Check the version file within the QcalAgent package directory, typically found in the application metadata or via the QNAP interface (App Center > QcalAgent > Details). Alternatively, look for a version file in the QcalAgent installation path.
    Affected if The displayed version number is lower than 1.1.7 or the version cannot be determined (indicating an old installation)
  3. Verify the QcalAgent web interface is accessible
    Attempt to access the QcalAgent web interface via the QNAP device's IP address on the default port (typically port 8080 or as configured during installation), for example: http://[QNAP-IP]:[port]/qcalagent/
    Affected if The web interface loads successfully and the application is actively running
  4. Confirm the application handles user input
    Review QcalAgent configuration files in its installation directory for any web-facing parameters or input fields that process user data without sanitization.
    Affected if User-accessible input fields or parameters exist in the application configuration

The environment is affected if QcalAgent version is installed and is lower than version 1.1.7, with the web interface accessible for exploitation.

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.1.7 or later
Fixed in 1.1.7
Interim mitigation

Update QcalAgent to version 1.1.7 or later to remediate the vulnerability.

Recommended fix High confidence

QcalAgent 1.1.7

  1. Check the current version of QcalAgent installed on the QNAP device
  2. Navigate to the QNAP download center at www.qnap.com or access the QNAP App Center
  3. Download QcalAgent version 1.1.7 or later
  4. Install or update QcalAgent through the QNAP interface or App Center
  5. Verify the installed version is 1.1.7 or higher

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

Fix this in Qcalagent Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $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 $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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