VulnCrest
Search
Create account
Report an incident
Radar sectionsDatabase
Check my site
WordPress plugin

WP2Speed Faster – Optimize PageSpeed Insights Score 90-100 <= 1.0.1 — Improper Authorization due to use of Hardcoded Credentials

CVE-2024-5810Published · Updated

Action summary

Affected: ≤1.0.1No patch available

What to do until a fix ships
Watch plugin
Severity
Medium5.3
CVSS
5.3
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:N Privileges required
None
UI:N User interaction
None
S:U Scope
Unchanged
C:N Confidentiality
None
I:L Integrity
Low
A:N Availability
None
Weakness
CWE-798 Use of Hard-coded Credentials
Required access
No account needed
Exploit prediction (EPSS)
No score
CISA KEV
Not listed
On this page8

Am I affected?

WP2Speed Faster – Optimize PageSpeed Insights Score 90-100 wp2speed

  1. Affected≤ 1.0.1
  2. PatchedNo fix yet

No patched version available.

You are affected if you run ≤ 1.0.1. No fixed version has been released.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under WP2Speed Faster – Optimize PageSpeed Insights Score 90-100.
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch WP2Speed Faster – Optimize PageSpeed Insights Score 90-100 to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Lucio Sá.

The WP2Speed Faster – Optimize PageSpeed Insights Score 90-100 plugin for WordPress is vulnerable to unauthorized access in all versions up to, and including, 1.0.1. This is due to the use of hardcoded credentials to authenticate all the incoming API requests. This makes it possible for unauthenticated attackers to overwrite CSS, update the trial settings, purge the cache, and find attachments.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in WP2Speed Faster – Optimize PageSpeed Insights Score 90-100

All 2
More vulnerabilities in WP2Speed Faster – Optimize PageSpeed Insights Score 90-100
SeverityVulnerabilityCVEPublished
Medium5.3Unauthenticated Information Exposure
≤1.0.1No patch available
CVE-2024-37924

Timeline

  1. CVE published

    Severity medium, CVSS 5.3

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
CVE® identifiers
Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Jump to

Are you sure?