Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Uncaught Error: Class 'ParagonIE_Sodium_Core32_Curve25519' not found #143

Closed
x-Felix opened this issue Mar 28, 2022 · 4 comments
Closed

Comments

@x-Felix
Copy link

x-Felix commented Mar 28, 2022

PHP Fatal error: Uncaught Error: Class 'ParagonIE_Sodium_Core32_Curve25519' not found in /wordpress/wp-includes/sodium_compat/src/Core32/Ed25519.php:10\nStack trace:\n#0 {main}\n thrown in /wordpress/wp-includes/sodium_compat/src/Core32/Ed25519.php on line 10, referer: http://example.com/wp-includes/sodium_compat/src/Core32/Ed25519.php

I saw lot of error messages in Apache log.
wordpress 5.9.2. Not really have idea what triggers the php error.

@paragonie-security
Copy link
Contributor

paragonie-security commented Mar 29, 2022

That looks like an autoloader bug. What version of PHP are you running?

Try adding this snippet at the top of wp-includes/sodium_compat/src/Core32/Ed25519.php:

if (!class_exists('ParagonIE_Sodium_Core32_Curve25519')) {
    require_once dirname(__FILE__) . '/Curve25519.php';
}

If that doesn't fix it, restart your webserver.

@x-Felix
Copy link
Author

x-Felix commented Mar 30, 2022

Thanks. My php version is 7.4.28.
I added the line and haven’t seen error message yet.

@paragonie-security
Copy link
Contributor

Okay, I'll add this in #145 and do a new point release this week so the fix is official.

In the meantime, if anyone wants to try to identify the actual cause of the autoloader bug, that might make for an interesting write-up.

@bporcelli
Copy link

@paragonie-security For what it's worth the only way I've been able to reproduce this is by accessing the file /wp-includes/sodium_compat/src/Core32/Ed25519.php directly (which makes sense, since the autoloader won't be loaded in that case). As far as I can tell this doesn't happen when sodium_compat is loaded correctly.

Perhaps it's an attempt at "google dorking" as leonardorodriguez guesses in https://wordpress.org/support/topic/sodium-compact-security-hole-maybe-google-dorking/ 🤔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants