WPIntell

Source evidence

Security check failed. Please try again

CryptX · support · 2025-12-11T08:54:00+00:00

mixedsentiment
highseverity
0.95relevance
10replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

5 / 34 rows with source links

14.7% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

29 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
dragon013 resolved
Hello, after an update to 4.0.7 I get the message “ Security check failed. Please try again ” whenever I try to save any options on my wordpress installation. Commenting out line 102 in cryptx.php solved the problem for now. Please have a look into this. Thanks! Dragon Hallo, das kann ich bestätigen. Ich habe vorhin festgestellt, dass kein Benutzer einen Beitrag veröffentlichen oder aktualisieren, Plugins deaktivieren oder aktivieren oder Optionen speichern konnte, auch Administratoren nicht. Komischerweise war das Veröffentlichen und Bearbeiten von Inhalten mit dem Block-Editor möglich, aber nicht mit dem Classic Editor. — Hello, I second this. I noticed earlier that no user was able to publish or update posts, deactivate or activate plugins, or save options, not even administrators. Strangely enough, it was possible to publish and edit content with the block editor, but not with the classic editor. Same problem here, this update causes massive problems, can’t safe ACF fields, etc. Yeah same here. Unable to publish ar save draft (also legacy editor). But also unable to active or desactive plugin by the UI. Had to desactivate the plugin by sftp. This reply was modified 6 months, 3 weeks ago by Alexis . I can only apologize. The check of the _wpnonce field should, of course, only be performed if data has been sent from the CryptX settings page. Why I removed the check from the code before uploading the version remains a mystery to me. The problem is fixed in version 4.0.8 and should already be available. Thanks for reporting the problem 👍 Just installed 4.0.8 and everything seems to be ok again. Thanks for that fast reaction! Thanks for the quick fix, it’s also working now for me. But I get this warning in my local environment (PHP 8.4.15), maybe you’d like to have a look at it: Undefined array key “tab” in /Users/Me/Sites/localhost/PPP/wp-content/plugins/cryptx/classes/Admin/GeneralSettingsTab.php on line 124 Hi @kl0082 , I also found this warning; it’s already fixed locally on my system and will be available with the next update. Thanks for the heads-up. Hello Ralf, I have the problem that I can not update to version 4.0.8. It’s not possible because also there the error “Security check failed. Please try again.” appears. Deactivating of the plugin also impossible. Do you have a solution for me? Thanks and best! Hi @gokeeffe87 , The easiest way would probably be to delete the directory “wp-content/plugins/cryptx” (but only the cryptx directory!) on your web server and then install the latest version from the WordPress repository. PS: A review of the plugin helps other users and me 😀 Thanks Ralf! I didn’t had FTP access. But I have it now, and then renaming the plugin was quick and easy. So it’s working again 🙂 Best, Nadine

Comments

10 shown
Machtnix 2025-12-11T09:07:00+00:00

Hallo, das kann ich bestätigen. Ich habe vorhin festgestellt, dass kein Benutzer einen Beitrag veröffentlichen oder aktualisieren, Plugins deaktivieren oder aktivieren oder Optionen speichern konnte, auch Administratoren nicht. Komischerweise war das Veröffentlichen und Bearbeiten von Inhalten mit dem Block-Editor möglich, aber nicht mit dem Classic Editor. — Hello, I second this. I noticed earlier that no user was able to publish or update posts, deactivate or activate plugins, or save options, not even administrators. Strangely enough, it was possible to publish and edit content with the block editor, but not with the classic editor.

kl0082 2025-12-11T09:19:00+00:00

Same problem here, this update causes massive problems, can’t safe ACF fields, etc.

Alexis 2025-12-11T09:30:00+00:00

Yeah same here. Unable to publish ar save draft (also legacy editor). But also unable to active or desactive plugin by the UI. Had to desactivate the plugin by sftp. This reply was modified 6 months, 3 weeks ago by Alexis .

Ralf Weber 2025-12-11T09:38:00+00:00

I can only apologize. The check of the _wpnonce field should, of course, only be performed if data has been sent from the CryptX settings page. Why I removed the check from the code before uploading the version remains a mystery to me. The problem is fixed in version 4.0.8 and should already be available. Thanks for reporting the problem 👍

dragon013 2025-12-11T09:54:00+00:00

Just installed 4.0.8 and everything seems to be ok again. Thanks for that fast reaction!

kl0082 2025-12-11T10:28:00+00:00

Thanks for the quick fix, it’s also working now for me. But I get this warning in my local environment (PHP 8.4.15), maybe you’d like to have a look at it: Undefined array key “tab” in /Users/Me/Sites/localhost/PPP/wp-content/plugins/cryptx/classes/Admin/GeneralSettingsTab.php on line 124

Ralf Weber 2025-12-11T10:32:00+00:00

Hi @kl0082 , I also found this warning; it’s already fixed locally on my system and will be available with the next update. Thanks for the heads-up.

gokeeffe87 2026-01-06T06:41:00+00:00

Hello Ralf, I have the problem that I can not update to version 4.0.8. It’s not possible because also there the error “Security check failed. Please try again.” appears. Deactivating of the plugin also impossible. Do you have a solution for me? Thanks and best!

Ralf Weber 2026-01-06T12:03:00+00:00

Hi @gokeeffe87 , The easiest way would probably be to delete the directory “wp-content/plugins/cryptx” (but only the cryptx directory!) on your web server and then install the latest version from the WordPress repository. PS: A review of the plugin helps other users and me 😀

gokeeffe87 2026-01-15T16:23:00+00:00

Thanks Ralf! I didn’t had FTP access. But I have it now, and then renaming the plugin was quick and easy. So it’s working again 🙂 Best, Nadine