dbcve.org
Teamwork Cloud No Magic ReleaseApplication · 3ds

CVE-2023-3588

MEDIUM · 5.4 CVSS v3.1 Published 2023-09-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
A stored Cross-site Scripting (XSS) vulnerability affecting Teamwork Cloud from No Magic Release 2021x through No Magic Release 2022x allows an attacker to execute arbitrary script code.

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

A stored Cross-site Scripting (XSS) vulnerability in Teamwork Cloud (versions 2021x through 2022x) allows malicious script code to be persistently injected and executed in the context of other users' sessions when the stored content is rendered.

MitigationImplement contextual output encoding and input validation/sanitization on all user-supplied data fields; apply Content Security Policy headers to mitigate script execution; vendor may have released patches in later versions.

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
Teamwork Cloud No Magic ReleaseApplication
Affected:= 2021x= 2022x

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. Identify Teamwork Cloud installed version
    Access the administration console or check the product installation directory for version information. Common locations include the About section in the admin UI or version file in the installation root.
    Affected if The installed version is 2021x or 2022x (any minor release within these major versions)
  2. Locate user-supplied data input fields
    Review the Teamwork Cloud application for areas where users can submit or upload content that gets stored persistently, such as project descriptions, comments, documentation fields, or user profile information.
    Affected if User-supplied data fields exist and accept content that is stored in the database for later retrieval and display to other users
  3. Inspect stored content rendering
    Submit test content containing HTML or script tags (such as <script>alert('test')</script>) into user input fields, then view that content as a different user account to observe if the tags execute or are displayed as raw text.
    Affected if The injected script tags execute or the browser interprets the HTML rather than displaying it as plain text (indicating lack of contextual output encoding)
  4. Verify input validation configuration
    Check the application configuration files or security settings for input validation and sanitization mechanisms. Look for whitelist patterns, input length limits, or sanitization libraries configured for user inputs.
    Affected if No input validation or sanitization is configured for user-supplied data fields, or validation can be bypassed
  5. Review Content Security Policy headers
    Use browser developer tools or a HTTP header inspection tool to examine the CSP headers returned by Teamwork Cloud server responses. Check if script-src directive allows inline scripts or untrusted sources.
    Affected if Content-Security-Policy headers are missing, not configured, or allow 'unsafe-inline' for script execution, providing no defense-in-depth mitigation

You are affected if running Teamwork Cloud version 2021x or 2022x and user-supplied content is rendered without proper output encoding, allowing stored XSS execution across user sessions.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement contextual output encoding and input validation/sanitization on all user-supplied data fields; apply Content Security Policy headers to mitigate script execution; vendor may have released patches in later versions.

Fix this in Teamwork Cloud No Magic Release Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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