CVE-2025-1648: The Yawave plugin for WordPress is vulnerable to SQL Injection via the 'lbid' parameter in all versions up to,

Q: How do I fix CVE-2025-1648?

yawave: upgrade to newer than 2.9.1. Exact commands for each OS are on this page.

Q: Is CVE-2025-1648 being exploited?

CVE-2025-1648 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-1648 affect?

CVE-2025-1648 affects yawave. Severity is high (CVSS 7.5). The Yawave plugin for WordPress is vulnerable to SQL Injection via the 'lbid' parameter in all versions up to, and including, 2.9.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existi

Q: How urgent is CVE-2025-1648?

Priority 52/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

HIGH 7.5REMOTEUPGRADE

CVE-2025-1648 is a high-severity flaw (CVSS 7.5) affecting yawave. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Yawave plugin for WordPress is vulnerable to SQL Injection via the 'lbid' parameter in all versions up to, and including, 2.9.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.0% (top 38%)
CISA exploited list	No
Weakness	CWE-89
Published	2025-02-25
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: yawave

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-02-25 07:15 UTCPublished CVE record published
2026-06-17 08:39 UTCUpdated Record last modified

yawave yawave UPGRADE

Affected: <= 2.9.1

Fixed in: newer than 2.9.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy yawave || rpm -q yawave || yawave --version

2. UPGRADE to newer than 2.9.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade yawave

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade yawave

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-1648?

yawave: upgrade to newer than 2.9.1. Exact commands for each OS are on this page.

Is CVE-2025-1648 being exploited?

CVE-2025-1648 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-1648 affect?

CVE-2025-1648 affects yawave. Severity is high (CVSS 7.5). The Yawave plugin for WordPress is vulnerable to SQL Injection via the 'lbid' parameter in all versions up to, and including, 2.9.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existi

How urgent is CVE-2025-1648?

Priority 52/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs