CVE-2026-4306
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe WP Job Portal WordPress plugin (versions up to 2.4.8) contains an unauthenticated SQL injection vulnerability in the 'radius' parameter. The plugin fails to properly escape user input and does not use prepared statements, allowing attackers to inject arbitrary SQL queries and potentially extract sensitive data from the database.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify WP Job Portal plugin is installedCheck for the plugin directory at wp-content/plugins/wp-job-portal/ or look for the plugin in WordPress admin under Plugins > Installed PluginsAffected if Plugin is not present in the installation
-
Check installed plugin versionView the plugin version in the plugin header (wp-content/plugins/wp-job-portal/wp-job-portal.php) or in the plugin's readme.txt file under the 'Stable tag' fieldAffected if Version is 2.4.8 or lower
-
Identify the radius parameter endpointLocate the PHP file(s) handling the 'radius' parameter search functionality - typically in the job search or location-based query handlers within the plugin's includes or controller foldersAffected if The radius parameter feature exists and processes user input
-
Verify SQL query lacks prepared statementsOpen the identified file handling the radius parameter and inspect the database query code - look for direct use of $_REQUEST['radius'] or similar in SQL statements without $wpdb->prepare() or proper escapingAffected if The radius parameter is used in raw SQL queries without $wpdb->prepare() or parameterized queries
You are affected if WP Job Portal plugin version is 2.4.8 or lower AND the radius parameter feature is accessible/used in your environment with SQL queries that lack prepared statements.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to version 2.4.9 or later which contains the fix. Until then, consider disabling the plugin or implementing WAF rules to block SQL injection attempts targeting the 'radius' parameter.
Upgrade to WP Job Portal version 2.4.9 or higher
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find the WP Job Portal plugin
- Click 'Update now' if an update is available, or manually upload version 2.4.9 or higher from the WordPress plugin repository
- Verify the update was successful by checking the plugin version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-4306 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-4306 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data