What is CVE-2009-3731?A medium-severity flaw in Epublisher, explained.
CVE-2009-3731 is a medium-severity flaw (CVSS 4.3) in Epublisher from Webworks, published on 16 December 2009. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 2.8%. If you run an affected version, plan in the vendor’s fix.
Published 16 December 2009. Record last updated 16 June 2026. We keep this page's data up to date.
What is CVE-2009-3731? In plain terms.
It can be attacked from anywhere on the internet without logging in. If it works, the attacker can change some data.
Multiple cross-site scripting (XSS) vulnerabilities in WebWorks Help 2.0 through 5.0 in VMware vCenter 4.0 before Update 1 Build 208156; VMware Server 2.0.2; VMware ESX 4.0; VMware Lab Manager 2.x; VMware vCenter Lab Manager 3.x and 4.x before 4.0.1; VMware Stage Manager 1.x before 4.0.1; WebWorks Publisher 6.x through 8.x; WebWorks Publisher 2003; and WebWorks ePublisher 9.0.x through 9.3, 2008.1 through 2008.4, and 2009.x before 2009.3 allow remote attackers to inject arbitrary web script or HTML via (1) wwhelp_entry.html, reachable through index.html and wwhsec.htm, (2) wwhelp/wwhimpl/api.htm, (3) wwhelp/wwhimpl/common/html/frameset.htm, (4) wwhelp/wwhimpl/common/scripts/switch.js, or (5) the window.opener component in wwhelp/wwhimpl/common/html/bookmark.htm, related to (a) unspecified parameters and (b) messages used in topic links for the bookmarking functionality.
What kind of flaw is it?
- CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beAnywhere on the internet
- How hard it is to pull offSome conditions needed
- Login needed firstNo login needed
- What an attacker getsCan change some data
Severity vector: AV:N/AC:M/Au:N/C:N/I:P/A:N
Is CVE-2009-3731 being exploited? Not that we know of.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 2.8%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Record last updated
CVE-2009-3731 scores 16. Action: Track.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isSmaller factor
- Threat activity around itSmaller factor
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2009-3731 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2009-3731? 10 products.
The published record lists 10 products from 2 vendors. If you run one of these, check your version, then go to the fix below.
- Application
Epublisher
by Webworks
Affected versions9.09.19.29.32008.12008.22008.32008.42009.12009.2 - Application
Help
by Webworks
Affected versions2.03.04.05.0 - Application
Publisher
by Webworks
Affected versions6.07.08.02003 - Application
Vcenter Lab Manager
by VMware
Affected versions3.03.0.13.0.24.0 - Application
Esx Server
by VMware
Affected versions4.0 - Application
Lab Manager
by VMware
Affected versions2.0 - Application
Server
by VMware
Affected versions2.0.2 - Application
Stage Manager
by VMware
Affected versionsup to 4.0 - Application
Vcenter
by VMware
Affected versions4.0
How do I fix CVE-2009-3731? Four steps.
- Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
- Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisories and patch notes first in the list.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.
Does CVE-2009-3731 affect you? 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.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- 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.
1 new flaw affects software Acme tracks
Multiple cross-site scripting (XSS) vulnerabilities in WebWorks Help 2.0 through 5.0 in VMware vCenter 4.0 before Update 1 Build 208156; VMware Server 2.0.2;...
- Matched to
- Epublisher on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2009-3731 is a medium-severity flaw in Epublisher from Webworks, published on 16 December 2009. It can be attacked from anywhere on the internet without logging in. If it works, the attacker can change some data.
It scores 4.3 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2009-3731 is 16 out of 100, which is Info. Its action is "Track". No sign of exploitation and a low forecast. Patch it in your normal update cycle.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 2.8%. That can change at any time, which is why we keep watching.
For Epublisher from Webworks: 9.0, 9.1, 9.2, 9.3, 2008.1, 2008.2 and 4 more. The record lists 10 products in all, each with its versions, under "Who is affected" on this page.
Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.