The announcement in PC World (and in other media)
is very unclear.
The bug seems to be fixed already in Firefox 2.0.0.2
and Seamonkey 1.1.1, if a read the announcement of
the Mozilla Foundation from March, 5th correctly. See here :
http://www.mozilla.org/security/announce/2007/mfsa2007-09.html
In the press it gives the impression of an additional fix,
which I cannot find anywhere.
As my GRE for my Linux-usable version and my update 5 for
KM 0.9.13 dates from a Seamonkey nightly of February, 21st,
I presume, that the fix is already included there, as the
latest Firefox 2.0.0.2 was released on February, 24th .
Fred