WHMCS Chris

Hello, Have you submitted a ticket with us so we can take a look? http://www.whmcs.com/get-support Thanks!

Hello, As it's been noted, this particular user is attempting to exercise an old vulnerability that has been corrected for some time now. Unfortunately, without deeper seated solutions, mitigation of this comes at a cost. If you'd like to mitigate this without the below proposed, you can lock sepecific client fields such that the user cannot modify them after registration: http://docs.whmcs.com/Other_Tab#Locked_Client_Profile_Fields This would effectively turn this on for all clients of course. The alternative, would use mod_security which most standard mod_security rules already perform blocks against AES_DECRYPT calls, such as AtomicCorp or TrustWaves. Example: https://www.atomicorp.com/products/products-comparison.html Ultimately, if you're running any sort of web application you should have some level of server side protection enabled. Be it grsec kernels, mod_security, etc I'm going to close the thread at this time to allow this to be the last response for any other individuals experiencing the same problem. If you want to reach out and discuss server level protection a bit more please feel free to send me a PM and I'll be happy to assist.

Woohoo! Congrats Alex!

Hello, As InfoPro mentioned, providing your ticket ID will help us identify the issue. However to note, Technical Support is available 24x7, Customer Service & Sales is only available Monday-Friday, 6am to 9pm BST. The Customer Service & Sales department would have been those handling your pending order request. You can view our teams availability here: http://www.whmcs.com/get-support/

Hello, This is being caused by EOL versions of PHP and the change in how filter_flag_ipv6 changed in versions newer than PHP 5.3.6. Updating PHP would resolve this.

Hello, This is shown in the ticket view(between the reply box, and the stored replies), highlighted in a light blue. It's only shown if someone selects a related service of course.

Hello, The primary concern is that PHP5.5 deprecates MySQL support (http://www.php.net/manual/en/migration55.deprecated.php). This is a functionality that WHMCS currently relies on.

Looks good - looking forward to checking it out.

Hello, Currently not - we are an installed application. However can recommend a variety of hosting providers that can host this application for you.

To me, it sounds like a server side issue with PHP. Are you able to load PHP pages elsewhere?

Can you submit a ticket? I'm unable to reproduce this -> please provide your ticket ID as well so i can go in and look for it. Thanks!

Hello, There is an administration password you must enter to confirm the action you wish to take is accurate. It is above the submission button.

Hello, When posting these types of posts - it would be extremely helpful if you supplied your ticket along with it so we can take a look. Additionally, we currently treat each ticket with the same priority, which is that it is answered in the order that it was received. Due to the recent software updates, there have been a very large number of tickets coming into the ticket system so our response time has delayed due to this. For that, I absolutely apologize. Additionally, if you're posting in the forums - you may want to ask other users if they've run into a similar issue, as they may be able to provide assistance while you wait for Technical Support to respond. Thank you, and again sorry for the delay.

Hello, I've created a sticky post for this -> http://forums.whmcs.com/showthread.php?81110-Case-3325-v5-2-12-Credit-Cards-not-processing-correctly&p=346230#post346230

Due to a bug in the latest release, there have been a number of users experiencing credit cards not processing correctly when using the weekly retries option. This does not affect users using the attempt only once or attempt captures daily processing options. We expect to release a maintenance update next week which will include a fix, but in the meantime we are providing a hot-fix due to the nature of this issue via the forums to allow you to patch the issue in the current release. Applying the Patch To apply the patch, download this zip file CCWeeklyRetriesFix.zip, unzip and upload the file contained within it to the /includes/ folder of your WHMCS installation. This is applicable only to 5.2.12 If you have been affected by this, and as a result have some invoices which have not been attempted, we have a solution for you to attempt captures on those invoices once you have applied the patch. To do this, navigate to Setup > Automation Settings and in the Process Days Before Due setting, enter a negative value of -1. You can then proceed to attempt captures via the option on the admin homepage and this will attempt to capture due invoices as if it were yesterday. You can repeat this for values of -2, -3, etc... in the Process Days Before Due setting field in order to run the captures for previous days also. Once you're done just remember to set the Process Days Before Due value back to what it was before. We apologize for the inconvenience this has caused.

I put a redirect in place and got in contact with PayPal - thanks for reporting this guys!

This looks really nice. Great job!

Hey guys, Support has this patch readily available. The hold is due to wanting to release another update with a number of maintenance updates as well. We anticipate this next week, however it may change of course. There's another thread that correlates to this issue which we've described how to obtain the patch.

Hello, Do you guys have ticket's open? If so, what's the ticket ID?

Hello, I'm still seeing this on my dev install - do you have a ticket in currently?

Not a problem - by all means ask around. However my response was to merely ensure you that no compromise has taken place of our servers.

Found it - Responded!

Jessica, Do you have a ticket #?

We've reviewed our SQL logs extensively. If customer data had been obtained, we would have made an immediate notification.

Hello, It's highly unlikely that it only took this individual a few days. It's more reasonable that he had a few and posted them in sequence intentionally causing a degree of panic. We are in the middle of performing internal auditing and reviewing new external auditors.