Re: CMS Made Simple 1.5 is in development
Posted: Wed Oct 29, 2008 2:13 pm
One of the open issues we're working on is the potential (medium threat) XSS opportunity in the admin interface of CMS.
We had an online development team meeting yesterday where we discussed this vulnerability, and the proper solution, and how/who will implement it.
Unfortunately, the implementation involves modifications to each and every form and link in the admin section. This will take a bit of time to finish... though there are four or five of us working on it so it shouldn't be too long. I'll crack the whip and get them going
Beta testing will be critical on this release, as we have had to modify just about everything in the admin to fix this problem. The more beta testers we can arrange the better.
As well, though most modules should work just fine without modification, some badly behaved or badly implemented modules may not be compatible with CMS version 1.5... I don't know which modules (if any) these are. and no, we will not support them or fix them just because they may now be broken. It will be up to the module developer(s) to fix these problems and release a new version.
Just thought I'd keep you informed.
We had an online development team meeting yesterday where we discussed this vulnerability, and the proper solution, and how/who will implement it.
Unfortunately, the implementation involves modifications to each and every form and link in the admin section. This will take a bit of time to finish... though there are four or five of us working on it so it shouldn't be too long. I'll crack the whip and get them going

Beta testing will be critical on this release, as we have had to modify just about everything in the admin to fix this problem. The more beta testers we can arrange the better.
As well, though most modules should work just fine without modification, some badly behaved or badly implemented modules may not be compatible with CMS version 1.5... I don't know which modules (if any) these are. and no, we will not support them or fix them just because they may now be broken. It will be up to the module developer(s) to fix these problems and release a new version.
Just thought I'd keep you informed.