There are a couple of options, but you have to weigh them against the risks. The reason for the change was to protect users, afterall.
One option is to use some of the online hints to go back to Java 6 - that is a horrific idea and puts your system at the greatest risk.
Another option is to manually modify XProtect in Safari to accept the 1.7.10r18 version as valid. This is also risky because there are active exploits in the wild for this version of Java. I'm not sure how often XProtect does its thing, but, if you manually modify the plist, you may have to do so repeatedly.
You can also run the developer version of Java, which is 1.7.12 - I don't believe this has a *fix* for the exploit that is currently being used, but, it will fool Safari into thinking you are running a newer version thatn 1.7.10r18.
Your final option is to wait. Oracle will likely update soon. If you really need Java, you can probably use Firefox and 1.7.10r18, but you still are running a risk of having your system compromised.