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

CVE-2025-54052

HIGH · 7.5 CVSS v3.1 Published 2025-08-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/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 Realtyna Realtyna Organic IDX plugin real-estate-listing-realtyna-wpl allows PHP Local File Inclusion.This issue affects Realtyna Organic IDX plugin: from n/a through <= 5.0.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 confidence

This is a CSRF vulnerability in Realtyna's Organic IDX WordPress plugin that allows PHP Local File Inclusion. An attacker could exploit this by tricking an authenticated administrator into clicking a malicious link, causing the browser to send forged requests that leverage the LFI to include and execute arbitrary PHP files from the local server.

MitigationUpdate the plugin to the latest version once available, or disable the plugin until a patch is released. Implement anti-CSRF tokens for all state-changing operations and add strict validation/sanitization on file inclusion paths.

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
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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 checks

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

  1. Identify if Organic IDX plugin is installed
    Check the WordPress plugins directory at wp-content/plugins/ for a folder named 'organic-idx' or similar naming pattern from Realtyna. Alternatively, log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins to look for 'Organic IDX' or 'Realtyna Organic IDX' in the list.
    Affected if The plugin folder or listing exists in the WordPress installation
  2. Determine the installed plugin version
    In the WordPress admin, find the Organic IDX entry in Plugins > Installed Plugins and note the version number displayed below the plugin name. Alternatively, open the main plugin PHP file (usually organic-idx.php or similar in the plugin folder) and look for the 'Version' header in the plugin comment block.
    Affected if The version number matches or precedes the vulnerable version range (check against official advisories if version ranges become available)
  3. Verify the plugin is active
    In WordPress admin under Plugins > Installed Plugins, confirm that Organic IDX shows as 'Active' (not 'Inactive' or 'Must-Use'). An inactive plugin typically cannot be exploited for this vulnerability.
    Affected if The plugin status shows as Active
  4. Inspect for file inclusion endpoints
    Examine the plugin's PHP files (particularly in the main plugin file and any files handling template or file requests) for usage of include, require, include_once, or require_once with user-controlled or insufficiently validated variables. Look for patterns like 'include($file)', 'require($_GET[...]', or similar dynamic file inclusion.
    Affected if File inclusion code exists that uses insufficiently sanitized input from request parameters
  5. Review access logs for exploitation indicators
    Search web server access logs (Apache, Nginx) for requests to the WordPress site containing suspicious query parameters that might indicate LFI probing, such as '?file=', '?template=', '?path=' pointing to PHP files in the plugin directory or wp-content. Also check for repeated POST requests from admin sessions that might indicate CSRF exploitation attempts.
    Affected if Logs contain requests with LFI-like parameters targeting the plugin, or anomalous POST requests to plugin endpoints from admin sessions

The environment is likely affected if the Organic IDX plugin is installed, active, and running a version within the vulnerable range, with file inclusion code present that could be exploited via CSRF.

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 the plugin to the latest version once available, or disable the plugin until a patch is released. Implement anti-CSRF tokens for all state-changing operations and add strict validation/sanitization on file inclusion paths.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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