PTC Vuforia Studio does not require a token; this could allow an attacker with local access to perform a cross-site request forgery attack or a replay attack.
Product
PTC Vuforia Studio vulnerabilities
6 published CVES affecting PTC Vuforia Studio, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 6
- Critical
- 1
- High
- 3
- Medium
- 1
- Low
- 1
- Unscored
- 0
- CISA KEV
- 0
Latest PTC Vuforia Studio CVEs
Newest publication first
-
HighCVSS 8.0 EPSS 0.24%
-
MediumCVSS 4.3 EPSS 0.50%
Before importing a project into Vuforia, a user could modify the “resourceDirectory” attribute in the appConfig.json file to be a different path.
-
CriticalCVSS 9.9 EPSS 0.66%
A user could use the “Upload Resource” functionality to upload files to any location on the disk.
-
HighCVSS 8.1 EPSS 0.45%
By changing the filename parameter in the request, an attacker could delete any file with the permissions of the Vuforia server account.
-
LowCVSS 3.3 EPSS 0.13%
An attacker with local access to the machine could record the traffic, which could allow them to resend requests without the server authenticating that the user or session are valid.
-
HighCVSS 7.5 EPSS 0.48%
The local Vuforia web application does not support HTTPS, and federated credentials are passed via basic authentication.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.