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

I Recommend This <= 3.7.2 — Authenticated (Subscriber+) SQL Injection via Shortcode

CVE-2014-125099Published · Updated

Action summary

Affected: ≤3.7.2Update to 3.7.3 or newer

All remediation steps
Watch plugin
Severity
High8.8
CVSS
8.8
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:L Privileges required
Low
UI:N User interaction
None
S:U Scope
Unchanged
C:H Confidentiality
High
I:H Integrity
High
A:H Availability
High
Weakness
CWE-89 SQL Injection
Required access
Unknown
Exploit prediction (EPSS)
No score
CISA KEV
Not listed
On this page8

Am I affected?

I Recommend This – Love/Like Button for WordPress Posts i-recommend-this

  1. Affected≤ 3.7.2
  2. Patched in3.7.3

Update to 3.7.3 or newer.

You are affected if you run ≤ 3.7.2. Version 3.7.3 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under I Recommend This – Love/Like Button for WordPress Posts.
  • No admin access? Run a passive check of your site. It reads public files only.

What to do

  1. Update to version 3.7.3, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch I Recommend This – Love/Like Button for WordPress Posts to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Oskar Adin.

The I Recommend This plugin for WordPress is vulnerable to SQL Injection via the 'post_type' attribute called via the plugin's shortcode in versions up to, and including, 3.7.2 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 permissions and above to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

Exploits & references

Proof-of-concept & detection

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

Advisories & patches

More in I Recommend This – Love/Like Button for WordPress Posts

All 5
More vulnerabilities in I Recommend This – Love/Like Button for WordPress Posts
SeverityVulnerabilityCVEPublished
Medium4.4Authenticated (Admin+) Stored Cross-Site Scripting
≤3.8.3Update to 3.9.0
CVE-2023-23673
Medium4.3Cross-Site Request Forgery
≤3.9.0Update to 3.9.1
CVE-2023-28696
High7.2Cross-Site Scripting
<3.8.2Update to 3.8.2
—
Critical9.8SQL Injection
<3.7.3Update to 3.7.3
CVE-2014-10376

Same weakness (SQL Injection)

All SQL Injection
Other SQL Injection vulnerabilities
SeverityVulnerabilityCVEPublished
High7.2Unauthenticated Stored Cross-Site Scripting via Comment User-Agent Header
EZ SQL Reports Shortcode Widget and DB Backup≤5.25.25Update to 5.26.45
CVE-2026-120688
Critical9.8Unauthenticated Arbitrary File Upload via File Upload via Public Form Submission
Chatterbug Forms – Fast, Flexible WordPress Form Builder≤1.0.2Update to 1.1
CVE-2026-125055
Critical9.8Unauthenticated PHP Object Injection to Remote Code Execution via 'form' Parameter
ELEX WordPress HelpDesk & Customer Ticketing System≤3.3.9Update to 3.4.0
CVE-2026-119077
Medium5.3Unauthenticated Sensitive Information Exposure in 'search' Parameter
Customer Reviews for WooCommerce≤5.127.0Update to 5.128.0
CVE-2026-121518

Timeline

  1. CVE published

    Severity high, CVSS 8.8

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. [object Object] Licensed under the CC BY-SA 4.0.
CVE® identifiers
[object Object]. 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?