Better: a fix is available in CVS. If you have compelling reasons not to use it I'd say the risk is yours because the solution is already provided.
QUOTE (bid/17362/discuss)
This issue is due to a failure in the application to properly sanitize user-supplied input.
This has been a problem with PHP and apps for ages now and it keeps reappearing. IMHO what it means in essence is that those of you who use that stuff should start and keep urging developers and maintainers to follow safe coding rules that have existed for ages now. If, by the quality of their work, they indicate they are the type of developer that favours tinkering with adding new features over auditing and fixing problems in their existing code you know what you should do if you can't live with that.