CVE-2019-25745
Description
WordPress Plugin Google Review Slider 6.1 has a time-based blind SQL injection vulnerability in the 'tid' parameter, allowing unauthenticated attackers to extract database information.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
WordPress Plugin Google Review Slider 6.1 has a time-based blind SQL injection vulnerability in the 'tid' parameter, allowing unauthenticated attackers to extract database information.
Vulnerability
WordPress Plugin Google Review Slider version 6.1 contains a time-based blind SQL injection vulnerability. This vulnerability exists in the tid parameter, which is accessible via GET requests to the admin interface. The plugin is designed to store Google reviews locally in the WordPress database [1].
Exploitation
An unauthenticated attacker can exploit this vulnerability by sending crafted GET requests to the admin interface of the affected WordPress site. By manipulating the tid parameter with malicious SQL code, an attacker can trigger time delays in the database responses, enabling them to extract sensitive information through time-based blind SQL injection techniques [2].
Impact
Successful exploitation allows an unauthenticated attacker to extract sensitive database information. This is achieved by manipulating database queries and observing time-based differences in the server's responses, effectively performing a blind SQL injection to exfiltrate data [2].
Mitigation
Version 6.1 is affected by this vulnerability [2]. No specific patched version or release date is mentioned in the available references. Users are advised to update to a version that addresses this vulnerability once it becomes available. As of the current information, no workarounds or official patches have been disclosed [1, 2].
AI Insight generated on Jun 4, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
2- Range: <6.1
Patches
0No patches discovered yet.
Vulnerability mechanics
No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.
References
3News mentions
0No linked articles in our index yet.