Dear users of TYPO3,
Security vulnerabilities have been discovered in following third party TYPO3
extensions:
"Virtual Civil Services" (civserv)
"CWT Community" (cwt_community)
"Modern Guestbook / Commenting system" (ve_guestbook)
"FrontEnd MP3 Player" (fe_mp3player)
"Search In Tables" (fesearchintable)
"Content Search" (gst_contentsearch)
"Multilingual Alias" (multilingual_alias)
"Myth Repository" (myth_repository)
"References database" (t3references)
For further information on the issue in extension "CWT Community"
(cwt_community), please read the related advisory TYPO3-SA-2009-006 that was
published today:
<http: typo3.org teams security security-bulletins typo3-sa-2009-006></http:>
For further information on the issue in extension "Virtual Civil Services"
(civserv), please read the related advisory TYPO3-SA-2009-007 that was
published today:
<http: typo3.org teams security security-bulletins typo3-sa-2009-007></http:>
For further information on the issue in extension "Modern Guestbook /
Commenting system" (ve_guestbook), please read the related advisory
TYPO3-SA-2009-009 that was published today:
<http: typo3.org teams security security-bulletins typo3-sa-2009-009></http:>
For further information on all CSB (Collective Security Bulletin) issues ,
please read the related advisory TYPO3-SA-2009-008 that was published today:
<http: typo3.org teams security security-bulletins typo3-sa-2009-008></http:>
In general, the TYPO3 Security Team recommends to read the following pages:
The TYPO3 Security Cookbook:
<http: typo3.org fileadmin security-team typo3_security_cookbook_v-0.5.pdf>
Make sure you are subscribed to the TYPO3 Announce List:
<http: lists.netfielders.de cgi-bin mailman listinfo typo3-announce>
See all TYPO3 security advisories:
<http: typo3.org teams security security-bulletins></http:>
Regards,
Marcus Krause
Member of the TYPO3 Security Team
--
TYPO3 Security Team homepage: <a href="http://typo3.org/teams/security/" target="_blank" rel="noreferrer">http://typo3.org/teams/security/</a>
E-Mail: security@typo3.org
Please note: when replying to this e-mail, please leave the header intact.</http:></http:>