Wp Query ConsoleWordPress extension · Lubus
CVE-2024-50498
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 · uneditedImproper Control of Generation of Code ('Code Injection') vulnerability in Ajit Bohra WP Query Console wp-query-console allows Code Injection.This issue affects WP Query Console: from n/a through <= 1.0.
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 · moderate confidenceCode Injection vulnerability in the WP Query Console WordPress plugin allows attackers to inject malicious code through improper control of code generation. This likely involves user-supplied input being directly used in code execution without proper sanitization, potentially allowing arbitrary PHP code execution on the WordPress server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Wp Query ConsoleWordPress extension
<= 1.0CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Locate the WP Query Console plugin installationCheck if the plugin directory exists in your WordPress installation at /wp-content/plugins/wp-query-console/ or similar path containing 'wp-query-console'Affected if The plugin directory exists in the plugins folder
-
Determine the installed plugin versionOpen the main plugin PHP file (typically wp-query-console.php) and locate the version header comment (e.g., 'Version: 1.0' or similar)Affected if The version is 1.0 or any version <= 1.0 (no fixed version is listed, so all versions up to and including 1.0 are affected)
-
Check if the plugin is activatedIn WordPress admin, navigate to Plugins > Installed Plugins and look for WP Query Console or WP Query Console by Lubus, or query the wp_options table for 'active_plugins'Affected if The plugin appears in the active plugins list or is present in the active_plugins option value
-
Identify if remote code execution features are accessibleCheck plugin settings or public-facing endpoints that allow query execution. Look for admin menu items labeled 'WP Query Console', 'Query Console', or similar, and examine if unauthenticated or low-privilege users can access query execution functionalityAffected if The plugin provides a query execution interface accessible to users without administrator privileges, or the interface is exposed without authentication
-
Review server access logs for suspicious requestsExamine web server access logs (Apache/nginx) for POST requests to paths containing 'wp-query-console', 'query-console', or 'wp-ajax' endpoints related to the plugin, especially with encoded or eval-like patterns in the request bodyAffected if Recent logs contain requests with code-like patterns, encoded strings, or suspicious query parameters targeting the plugin endpoints
Your environment is affected if the WP Query Console plugin by Lubus is installed and activated, regardless of version (affected versions are <= 1.0), and the query execution feature is accessible to users or exposed without proper sanitization controls.
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.
From vendor dataImmediately restrict access to or disable the WP Query Console plugin until a patched version is available; review server logs for indicators of compromise; implement strict input validation if the plugin is required for operations.
Fix this in Wp Query Console
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-50498 — 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-2024-50498 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