dbcve.org
Vuforia StudioApplication · Ptc

CVE-2023-27881

CRITICAL · 9.9 CVSS v3.1 Published 2023-06-07
Fix available
A fix is available. Upgrade to 9.9 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 user could use the “Upload Resource” functionality to upload files to any location on the disk.

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 path traversal vulnerability in the 'Upload Resource' functionality allows authenticated users to specify arbitrary file system paths as upload destinations. The application fails to properly validate or sanitize the target path provided during file uploads, enabling an attacker to write files to any location on the disk accessible by the application process.

MitigationImplement strict path validation to ensure uploaded files can only be written to designated, safe directories. Validate that the target path resolves within an allowed base directory, strip directory traversal sequences (..), and restrict upload permissions to least-privilege principles.

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
Vuforia StudioApplication
Affected:< 9.9

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 Ptc Vuforia Studio is installed
    Locate Vuforia Studio installation directories or check for associated services/processes on the system. Common paths include C:\Program Files\PTC\Vuforia Studio or installation directories specified during setup.
    Affected if Vuforia Studio is not found on the system, then the CVE does not apply.
  2. Determine the installed Vuforia Studio version
    Check the version of Vuforia Studio by examining the application files, registry entries, or the service information. Look for version metadata in the installation directory or use the application's version information utility if available.
    Affected if The installed version is any version prior to 9.9 (e.g., 9.8, 9.7, earlier).
  3. Verify the Upload Resource functionality exists
    Examine the Vuforia Studio web interface or API endpoints for a resource upload feature. Look for upload-related endpoints, forms, or modules that handle file uploads within the application.
    Affected if The Upload Resource functionality is present and accessible to authenticated users.
  4. Confirm authentication is not bypassed for uploads
    Review the access control configuration for the upload functionality to determine if unauthenticated access is possible. Check authentication settings in the application's configuration files or security settings.
    Affected if The upload endpoint is accessible to authenticated users without additional security restrictions that would prevent path traversal attacks.

A system is affected if Ptc Vuforia Studio version is installed and is below version 9.9, and the Upload Resource 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 9.9 or later
Fixed in 9.9
Interim mitigation

Implement strict path validation to ensure uploaded files can only be written to designated, safe directories. Validate that the target path resolves within an allowed base directory, strip directory traversal sequences (..), and restrict upload permissions to least-privilege principles.

Recommended fix Moderate confidence

Vuforia Studio 9.9

  1. 1. Back up the current Vuforia Studio installation and all associated data
  2. 2. Download Vuforia Studio version 9.9 or later from the official PTC distribution channel
  3. 3. Install the upgrade following the vendor's standard upgrade procedures
  4. 4. Verify that the 'Upload Resource' functionality now properly restricts file upload locations
  5. 5. Confirm the upgrade was successful and test that the unrestricted file upload vulnerability is remediated

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

Fix this in Vuforia Studio Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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