CVE-2025-4964
BaseFortify
Publication date: 2025-06-06
Last updated on: 2025-07-10
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| hk1993 | wp_online_users_stats | to 1.0.0 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The WP Online Users Stats plugin for WordPress has a time-based SQL Injection vulnerability in the 'table_name' parameter. This occurs because the plugin does not properly escape user input and does not sufficiently prepare the SQL query. As a result, authenticated users with Editor-level access or higher can inject additional SQL commands into existing queries, potentially extracting sensitive information from the database.
How can this vulnerability impact me? :
This vulnerability can allow attackers with Editor-level access or above to extract sensitive information from the WordPress site's database by injecting malicious SQL queries. This could lead to unauthorized disclosure of data, potentially compromising user information and site security.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include disabling or uninstalling the WP Online Users Stats plugin version 1.0.0 or earlier, as it has been closed and is not available for download pending a full review. Additionally, restrict Editor-level access and above to trusted users only, since the vulnerability requires authenticated users with such privileges. Monitor for plugin updates or patches once the review is complete before re-enabling the plugin. [1]