It appears that the vulnerability is with a particular CMS. Now the
example they have given is perl, the problem is that you can
potentially execute anything through the exploit, security through
obscurity is not absolute I generally leave obscurity to the birds,
you need to ensure your machine has not been compromised and then
follow your companies security procedures in resolving the issue.
With your CMS problem you have 2 options.
1. stop using the CMS that has the problem until they have fixed the
security flaw.
2. make sure the version of the CMS you have is not affected.
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html