Works vulnerabilitiesRanked by how likely they are to be used.

Product19 versions
The short answer

Works is made by Microsoft. We track 59 published vulnerabilities listed under that exact name, across 19 versions. None of them is on the list of flaws known to be exploited today. Microsoft lists newer releases under their own names, such as Works 6-9 File Converter, so check those pages too.

See the riskiest flaws

We keep watching the known-exploited list.

Other names

Is Works listed under other names? Yes.

Microsoft also lists Works under more specific names, such as Works 6-9 File Converter and Works Suite. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.

Known exploited

Which Works vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Works's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Works flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 52%

    A certain ActiveX control in WkImgSrv.dll 7.03.0616.0, as distributed in Microsoft Works 7 and Microsoft Office 2003 and 2007, allows remote attackers to execute arbitrary code or cause a denial of service (browser...

    CVSS9.3Published21 Apr 2008
  2. 48%

    Buffer overflow in wksss.exe 8.4.702.0 in Microsoft Works Spreadsheet 8.0 allows remote attackers to cause a denial of service (CPU consumption or crash) via crafted Excel files.

    CVSS2.6Published18 Jul 2006
  3. 44%

    Microsoft Works 6 File Converter, as used in Office 2003 SP2 and SP3, Works 8.0, and Works Suite 2005, allows remote attackers to execute arbitrary code via a .wps file with crafted section header index table...

    CVSS9.3Published12 Feb 2008
  4. 42%

    Buffer overflow in the converter for Microsoft WordPerfect 5.x on Office 2000, Office XP, Office 2003, and Works Suites 2001 through 2004 allows remote attackers to execute arbitrary code via a malicious document or...

    CVSS7.5Published28 Sep 2004
  5. 41%

    Unspecified vulnerability in Microsoft Word 2000, 2002, and Word Viewer 2003 allows user-assisted remote attackers to execute arbitrary code via a crafted DOC file that triggers memory corruption, as demonstrated via...

    CVSS9.3Published14 Dec 2006
  6. 40%

    Microsoft Office Word 2002 SP3, 2003 SP3, and 2007 SP2; Microsoft Office 2004 and 2008 for Mac; Open XML File Format Converter for Mac; Office Word Viewer; Office Compatibility Pack for Word, Excel, and PowerPoint...

    CVSS9.3Published11 Aug 2010
Precursor Intelligence

Running Works? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 59 published vulnerabilities listed under the name Works, across 19 versions.

None of Works's vulnerabilities is on the list of flaws known to be exploited today.

Microsoft also lists Works under more specific names, such as Works 6-9 File Converter and Works Suite. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.

Create a Precursor Intelligence account and track Works. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.