CVE-2025-2074 json
Advanced Google reCAPTCHA <= 1.29 - Authenticated (Subscriber+) Limited SQL Injection via 'sSearch' Parameter
published last yr. modified 4mo ago also EUVD-2025-8556
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 37%
- public exploits
- 0
- none known
Summary
The Advanced Google reCAPTCHA plugin for WordPress is vulnerable to generic SQL Injection via the ‘sSearch’ parameter in all versions up to, and including, 1.29 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Subscriber-level access and above, to append additional SQL queries into already existing queries, particularly when the plugin’s settings page hasn’t been visited and its welcome message has not been dismissed. This issue can be used to extract sensitive information from the database.
Patch / fix
- webfactoryltd advanced_google_recaptcha 1.30
Is CVE-2025-2074 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
0.43% chance of exploitation in the next 30 days, higher than 37% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected products
- webfactory Advanced Google reCAPTCHA
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/963a9b30-9194-4abc-aa69-eb333cbddef3?source=cve
- plugins.trac.wordpress.org /browser/advanced-google-recaptcha/trunk/libs/ajax.php?rev=3248228#L20
- plugins.trac.wordpress.org /browser/advanced-google-recaptcha/trunk/libs/ajax.php?rev=3248228#L277
- plugins.trac.wordpress.org /browser/advanced-google-recaptcha/trunk/libs/ajax.php?rev=3248228#L401
- plugins.trac.wordpress.org /browser/advanced-google-recaptcha/trunk/libs/admin.php?rev=3248228#L106
- plugins.trac.wordpress.org /browser/advanced-google-recaptcha/trunk/libs/setup.php?rev=3248228#L636
- wordpress.org /plugins/advanced-google-recaptcha/#developers
- plugins.trac.wordpress.org /changeset/3262396/
Sources
- CVE List CVE-2025-2074
- NVD CVE-2025-2074
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.