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

CVE-2026-4306 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%.

How to fix or mitigate CVE-2026-4306?

Within 24 hours: Audit all WordPress installations to identify if WP Job Portal plugin is installed and document affected systems. Within 7 days: Implement WAF rules blocking malicious radius parameter payloads, disable the plugin if non-critical, or restrict access via network segmentation. Within 30 days: Monitor vendor for patch release and prepare patching procedures; consider alternative job portal solutions if patch is not released within 90 days.

Wp Job Portal Ai Powered Recruitment System For Company Or Job Board Website CVE-2026-4306

EUVD-2026-14620 HIGH

SQL Injection (CWE-89)

2026-03-23 Wordfence

GHSA-p4fv-rjp4-q65f

WordPress SQLi Wp Job Portal Ai Powered Recruitment System For Company Or Job Board Website Wordpress Plugin Wpjobportal

7.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.5 HIGH

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

Re-analysis Queued

Apr 24, 2026 - 16:37 vuln.today

cvss_changed

EUVD ID Assigned

Mar 23, 2026 - 22:45 euvd

EUVD-2026-14620

Analysis Generated

Mar 23, 2026 - 22:45 vuln.today

CVE Published

Mar 23, 2026 - 22:25 nvd

HIGH 7.5

DescriptionCVE.org

The WP Job Portal plugin for WordPress is vulnerable to SQL Injection via the 'radius' parameter in all versions up to, and including, 2.4.8 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

The WP Job Portal plugin for WordPress contains an unauthenticated SQL injection vulnerability in the 'radius' parameter affecting all versions up to and including 2.4.8. Unauthenticated remote attackers can exploit this flaw to extract sensitive information from the database, including user credentials, personal data, and other confidential information stored in WordPress tables. The vulnerability has a CVSS score of 7.5 indicating high severity with no authentication required for exploitation.

Technical ContextAI

This vulnerability affects the WP Job Portal AI-Powered Recruitment System plugin (CPE: cpe:2.3:a:wpjobportal:wp_job_portal_–_ai-powered_recruitment_system_for_company_or_job_board_website:*:*:*:*:*:*:*:*), specifically in the job search functionality. The root cause is CWE-89 (SQL Injection), where the 'radius' parameter in the job model (model.php line 2743) lacks proper sanitization and parameterized query preparation. The vulnerability is accessible through the AJAX handler (includes/ajax.php line 10), allowing unauthenticated users to inject arbitrary SQL commands. The WordPress plugin architecture exposes this endpoint without requiring authentication, making it trivially accessible to remote attackers who can manipulate the radius parameter in HTTP requests to append malicious SQL statements to existing database queries.

RemediationAI

Upgrade WP Job Portal plugin to version 2.4.9 or later, which addresses this SQL injection vulnerability as evidenced by the changeset available at https://plugins.trac.wordpress.org/changeset?old_path=/wp-job-portal/tags/2.4.8&new_path=/wp-job-portal/tags/2.4.9. Site administrators should immediately update through the WordPress plugin manager or manually download the patched version from the WordPress plugin repository. Until patching is completed, consider temporarily disabling the WP Job Portal plugin if job search functionality is not critical to operations, or implement web application firewall (WAF) rules to block requests containing SQL injection patterns in the 'radius' parameter. Review database logs and access logs for suspicious queries or unusual data access patterns that may indicate prior exploitation, and consider rotating database credentials if compromise is suspected.