12
Hi wishcraft, Vaughan, JAVesey and all xoopers.
The issue here is advise the developer on the problem and this is completely ignored.
It is a pity that in my paiz not have a person who honestly tell me about a security point where is the problem and proposing a solution.
This is independent of cms being used. But there is a real difference in this aboradagem, verification of entry and verification of removal.
In this case, the module allows the failure to inject the malicious code, that is a fact and is proven.
The developer corrects this problem very quickly. But this does not guarantee that will be safe. The reason is the output of data. The hacker has prevented at the time the module has failed to deploy another code to extract data and using a javascript common?
The answer to this is the way to check the output of data. At this point there is a differential in favour of
XOOPS Cube and XOOPS and impresscms are still vulnerable.
What I am talking here is based on our experience in suffering with this type of problem, because we already know of some practices used by crakers and idiots who insist on trying misrepresenting the house outside.