Security Issue - Server Asset Folder

Are you aware that direct unsecure access can be made to the server asset area using the following URL (cms is the PowerCMS folder), you don't need a username or password to gain access.

index.php?lang=default&kfm_caller_type=fck&type=Image

Anyone else concerned about this?

This is fixed in Power CMS 2.1.1.

to fix it in earlier version. edit the HTMLEditor/editor/plugins/kfm/configuration.php file. change:

<?php require_once( "../../../../Connections/PowerCMSConnection.php" ); ?>

<?php require_once( "../../../WA_Globals.php" ); ?>

to:

<?php require_once( "../../../../Connections/PowerCMSConnection.php" ); ?>

<?php require_once( "../../../WA_Globals.php" ); ?>

<?php require_once( "../../../../WA_SecurityAssist/Helper_PHP.php" ); ?>

<?php

if (!WA_Auth_RulePasses("Administrator")){

    die();

}

?>

Great, thanks for your assistance...

Warning: Cannot modify header information - headers already sent by (output started at /home/vanguard/public_html/cmscontrol/HTMLEditor/editor/plugins/kfm/configuration.php:4) in /home/vanguard/public_html/cmscontrol/HTMLEditor/editor/plugins/kfm/includes/session.class.php on line 31

Warning: Cannot modify header information - headers already sent by (output started at /home/vanguard/public_html/cmscontrol/HTMLEditor/editor/plugins/kfm/configuration.php:4) in /home/vanguard/public_html/cmscontrol/HTMLEditor/editor/plugins/kfm/index.php on line 73

It looks like you might have an extra space character on line 4 of /HTMLEditor/editor/plugins/kfm/configuration.php.

That is just a guess... If you attach a copy of that page I can look into it further.

Thanks ray, you are correct there was an extra space in there, all working fine now...

It appears that I have the same exploit going on my PowerStore site. But my configuration.php file has this content -

<?php require_once( "../../../../Connections/PowerStoreConnection.php" ); ?>
<?php require_once( "../../../../webassist/framework/library.php" ); ?>
<?php
/**
* KFM - Kae's File Manager

How should I implement this fix?

There is a fix for this available in the Known Issues section of the Power Store download center page.

Jason, surely the fact that the fix is available should be publicised, I have a number of clients who have been affected by this issue and none of them were aware of this fix.