The idea futures software is unlikely to add any security holes, but people are encouraged to look at the source code to see if I've overlooked anything.
The system designed so that the cgi-scripts should only
be able to affect the system by sending commands to the server daemon.
User input is checked fairly carefully when it reaches the server
(see validate_fn in IFServer.py) to insure that strings
which will be evaluated by the database cannot contain characters that
might be used to execute arbitrary functions.
I believe the only other way that user can affect the filesystem through the idea futures web interface is when creating or modifying a claim, a .html file is written (see GenSearchFiles in IFClaim.py). The file names are strictly limited by the restrictions on what characters can be used in a claim symbol, and I can't see any way in which the files could be executed.
I have not yet done much analysis of the security weaknesses in the Python cpickle module which converts user input to Python objects to pass between cgi-scripts and the server.