I was initially going to suggest simply ignoring the CC number field in the form when you do the update SQL / transaction.
Just because it is provided by the user doesn't mean you have to use it.
But there is an issue with this - it assumes that a user will never be updating the credit card info with a different credit card - which I would suggest is a bad thing to "just" assume.
How about if you checked the submitted values for "*" characters in the credit card number?
If there are "*" they have NOT changed the CC number from what was originally saved, so therefore it is a "safe(r) bet", now that you can disregard the number.
If there are NO "*" - they have provided a CC number - validate it / re-save it.
Even if it is the same card number as before - just assume they have entered an entirely different number and perform your required CC number validation and then save all form data.
Something like;
<cfif form.ccNumber contains "*">
<!--- disregard the CC number it is the same as the old one --->
<!--- do other form field validation --->
<!--- save all OTHER form fields, only / do NOT save the CC number --->
<cfelse>
<!--- we have no "*" in the CC number - validate the card number --->
<!--- jQuery has credit card validation in its validation plugin. --->
<!--- do other form field validation --->
<!--- save ALL form fields --->
</cfif>