What is the CVSS score of CVE-2026-4834?

CVE-2026-4834 has a CVSS 3.1 base score of 7.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. EPSS exploitation probability: 0.1%.

Which versions of WP ERP Pro are affected by CVE-2026-4834?

WP ERP Pro WordPress plugin (versions through 1.5.1) contains an unauthenticated SQL injection vulnerability that allows remote attackers to extract sensitive database contents without…

How to fix or mitigate CVE-2026-4834?

Within 24 hours: Audit all WordPress installations for WP ERP Pro plugin presence and document running versions; implement Web Application Firewall rules to block SQL injection patterns on the 'search_key' parameter. Within 7 days: Contact WP ERP Pro vendor for patch timeline; enable database activity monitoring and review logs for suspicious queries; disable the plugin if non-critical. Within 30 days: Identify and pilot alternative solutions; develop version control and patch deployment strategy; implement least-privilege database access controls; prepare for immediate patching upon vendor release.

WP ERP Pro CVE-2026-4834

EUVD-2026-31391 HIGH

SQL Injection (CWE-89)

2026-05-22 Wordfence

GHSA-222q-9hw5-chw9

WordPress SQLi Wp Erp Pro Wedevs

7.5

CVSS 3.1 · Vendor: Wordfence

Severity by source

Vendor (Wordfence) PRIMARY

7.5 HIGH

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Primary rating from Vendor (Wordfence) · only source for this CVE.

CVSS VectorVendor: Wordfence

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

Analysis Generated

May 22, 2026 - 03:45 vuln.today

DescriptionCVE.org

The WP ERP Pro plugin for WordPress is vulnerable to SQL Injection via the 'search_key' parameter in all versions up to, and including, 1.5.1. This is 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.

AnalysisAI

Unauthenticated SQL injection in the WP ERP Pro WordPress plugin (versions through 1.5.1) allows remote attackers to extract sensitive database contents by manipulating the 'search_key' parameter. The flaw stems from missing input escaping and unprepared SQL statements, enabling UNION-based or appended query attacks against any WordPress site running the affected plugin. No public exploit identified at time of analysis, and the issue is not currently listed in CISA KEV.

Technical ContextAI

WP ERP Pro is a commercial WordPress plugin from weDevs (CPE: cpe:2.3:a:wedevs:wp_erp_pro) providing HR, CRM, and accounting functionality for WordPress-based business sites. The vulnerability is a classic CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), where the 'search_key' request parameter is concatenated into a SQL query without invoking WordPress's $wpdb->prepare() or proper escaping helpers like esc_sql(). Because WordPress plugins execute queries against the shared wp_ database - which stores user credentials, session tokens, and option values including API keys - any injection point grants broad read access to site secrets.

RemediationAI

Patch availability is not explicitly stated in the provided input - treat this as 'patch availability per vendor advisory not independently confirmed' and consult the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/d3849db8-5c9e-410e-be53-c9ab76162630 and the vendor at https://wperp.com/ for the fixed release (any version greater than 1.5.1 once published). Until a fixed version is installed, restrict access to the vulnerable endpoint via a WordPress WAF rule (Wordfence, Patchstack, or a generic mod_security rule blocking SQL metacharacters in the 'search_key' parameter), or temporarily deactivate the WP ERP Pro plugin if the ERP/CRM workflows can be paused - accepting the trade-off that HR and CRM features will be unavailable. Reviewing wp_users and wp_options for unexpected reads via access logs is also recommended; database credentials and any secrets stored in wp_options (API tokens, mail credentials) should be rotated if exploitation is suspected.