dbcve.org
Custom Query BlocksWordPress extension · Mediaron

CVE-2024-44059

MEDIUM · 5.4 CVSS v3.1 Published 2024-09-15
Fix available
A fix is available. Upgrade to after 5.3.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Ronald Huereca Custom Query Blocks post-type-archive-mapping allows DOM-Based XSS.This issue affects Custom Query Blocks: from n/a through <= 5.3.1.

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 confidence

DOM-based Cross-site Scripting (XSS) vulnerability in the Custom Query Blocks WordPress plugin (versions through 5.3.1) in the post-type-archive-mapping functionality allows authenticated attackers to inject malicious JavaScript through improper neutralization of input during web page generation.

MitigationUpdate Custom Query Blocks to the latest version (after 5.3.1) which should include proper input sanitization/encoding in the post-type-archive-mapping feature to prevent XSS attacks.

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
Custom Query BlocksWordPress extension
Affected:<= 5.3.1

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Custom Query Blocks plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'custom-query-blocks' or 'custom-query-blocks-template' or search in wp_options table for plugin-related options
    Affected if The plugin folder or database entries exist in the WordPress installation
  2. Check installed plugin version
    Open the main plugin PHP file (typically custom-query-blocks.php) and locate the version comment/constant at the top, or check the WordPress plugin admin page for the installed version
    Affected if The reported version is 5.3.1 or any version lower (e.g., 5.3.0, 5.2.9, etc.)
  3. Identify if post-type-archive-mapping feature is configured
    Search WordPress database (wp_options table) or plugin settings for options containing 'post_type_archive', 'archive_mapping', or 'cqb_post_type_archive' - these store the mapping configurations
    Affected if Any post-type-archive-mapping configuration records exist in the database
  4. Inspect stored mapping values for suspicious content
    Query the wp_options table for values related to post-type-archive-mapping and examine the data for unencoded HTML tags, script elements, or event handlers (onclick, onerror, etc.)
    Affected if The stored mapping values contain raw <script> tags, javascript: URIs, or HTML event attributes like onload, onerror, onclick
  5. Review page source for injected scripts in archive pages
    Visit WordPress archive pages (e.g., /?post_type=any or custom post type archives) and view page source, searching for unexpected script tags or inline event handlers in the post-type-archive-mapping output area
    Affected if Unexpected JavaScript code appears in the HTML source of archive pages, especially in areas controlled by the Custom Query Blocks plugin

A user is affected if the Custom Query Blocks plugin version is 5.3.1 or lower AND the post-type-archive-mapping feature has been configured with user-controlled input containing malicious scripts

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 5.3.1
Interim mitigation

Update Custom Query Blocks to the latest version (after 5.3.1) which should include proper input sanitization/encoding in the post-type-archive-mapping feature to prevent XSS attacks.

Fix this in Custom Query Blocks Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-44059 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-44059 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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