Directory traversal vulnerability in pdmwService.exe in SolidWorks Workgroup PDM 2014 allows remote attackers to write to arbitrary files v…

published 2015-01-13 11y ago modified 2026-06-17 4mo ago also EUVD-2014-1046

cvss: 6.4; version 2.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 57.4%; EPSS 57.4% chance of exploitation in 30 days, percentile 99%
public exploits: 3; Metasploit and Exploit-DB

Directory traversal vulnerability in pdmwService.exe in SolidWorks Workgroup PDM 2014 allows remote attackers to write to arbitrary files via a .. (dot dot) in the filename in a file upload.

Is CVE-2014-100015 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

2014-02-22 First public exploit (Metasploit exploit/windows/misc/solidworks_workgroup_pdmwservice_file_write)
2015-01-13 Published

Exploit prediction

57.37% chance of exploitation in the next 30 days, higher than 99% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

Metasploit exploit/windows/misc/solidworks_workgroup_pdmwservice_file_write SolidWorks Workgroup PDM 2014 pdmwService.exe Arbitrary File Write metasploit exploit, good rank, 2014-02-22
EDB-32163 SolidWorks Workgroup PDM 2014 - 'pdmwService.exe' Arbitrary File Write (Metasploit) remote, 2014-03-10
EDB-31831 SolidWorks Workgroup PDM 2014 SP2 - Arbitrary File Write remote, 2014-02-22
packetstormsecurity.com http://packetstormsecurity.com/files/125361 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	2.0	6.4	AV:N/AC:L/Au:N/C:N/I:P/A:P

Classification

Weakness

CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

exploit-db.com /exploits/32163
exploit
exploit-db.com /exploits/31831
exploit
packetstormsecurity.com /files/125361
exploit
exchange.xforce.ibmcloud.com /vulnerabilities/91518
vdb-entry

Sources

CVE List CVE-2014-100015
NVD CVE-2014-100015

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.