dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2024-53726

HIGH · 7.1 CVSS v3.1 Published 2024-12-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in RealtyCandy.com RealtyCandy IDX Broker Extended realtycandy-idx-broker-extended allows Stored XSS.This issue affects RealtyCandy IDX Broker Extended: from n/a through <= 1.5.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

Cross-Site Request Forgery (CSRF) vulnerability in the RealtyCandy IDX Broker Extended WordPress plugin enables attackers to inject malicious scripts (Stored XSS) through forged requests. The lack of proper CSRF protection allows authenticated or tricked administrators to execute unintended actions that persist malicious payloads within the plugin's settings or display areas.

MitigationUpdate to the latest patched version of RealtyCandy IDX Broker Extended. Until patched, implement anti-CSRF tokens in all plugin forms and sanitize all user-supplied input before storage and output.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

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 plugin installation
    Navigate to WordPress admin > Plugins and confirm 'RealtyCandy IDX Broker Extended' is installed and active
    Affected if Plugin is installed and active in WordPress
  2. Determine installed version
    In Plugins list, click the plugin name or view plugin file header to read the Version field
    Affected if Version is older than the patched version (any unpatched release is vulnerable)
  3. Inspect plugin forms for CSRF tokens
    View page source of plugin admin pages (IDX settings, display options, or frontend forms). Search for 'nonce' or 'csrf' in form HTML elements
    Affected if Forms lack nonce tokens or CSRF validation mechanisms in their HTML
  4. Check for stored XSS in plugin settings
    Navigate to plugin settings pages in admin panel. Examine input fields for IDX broker ID, display templates, or custom CSS areas for unexpected script tags or encoded content
    Affected if Unexpected script tags, iframe elements, or malformed HTML present in settings fields
  5. Review database for injected payloads
    Access WordPress database via phpMyAdmin or CLI. Query wp_options table for plugin-related option names containing suspicious JavaScript: SELECT * FROM wp_options WHERE option_name LIKE '%realtycandy%' OR option_value LIKE '%<script%'
    Affected if Plugin-related options contain script tags, event handlers, or base64-encoded malicious payloads

User is affected if the plugin is installed, running an unpatched version, and plugin forms lack CSRF nonce validation or malicious payloads already exist in settings.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest patched version of RealtyCandy IDX Broker Extended. Until patched, implement anti-CSRF tokens in all plugin forms and sanitize all user-supplied input before storage and output.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-53726 — 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-53726 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