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

CVE-2025-23557

HIGH · 7.1 CVSS v3.1 Published 2025-01-16
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 Kathleen Malone Find Your Reps find-your-reps allows Stored XSS.This issue affects Find Your Reps: from n/a through <= 1.2.

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

A Cross-Site Request Forgery (CSRF) vulnerability in the Find Your Reps WordPress plugin (version 1.2 and below) allows attackers to inject malicious scripts through unsanitized form submissions. This results in Stored XSS where the malicious payload is persisted and executed when administrators or users view the affected pages.

MitigationUpdate to the latest version of the Find Your Reps plugin when available; if no patch exists, disable the plugin. Implement anti-CSRF tokens on all state-changing form actions and ensure proper input sanitization and output encoding.

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 Find Your Reps plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Find Your Reps' in the list. Check if it is activated.
    Affected if The plugin is present and activated in WordPress.
  2. Determine installed plugin version
    Click 'View Details' on the Find Your Reps plugin in the Plugins page, or check the plugin's main PHP file header for the Version: X.X tag.
    Affected if The installed version is 1.2 or lower.
  3. Confirm form functionality is in use
    Navigate to the plugin settings page (Find Your Reps in the admin menu) and check if any representative lookup forms or address submission forms are configured and enabled on the site.
    Affected if The plugin's form submission feature is enabled and accessible on the site.
  4. Inspect stored form data for malicious scripts
    Access the WordPress database (via phpMyAdmin or WP-CLI) and query the wp_postmeta or custom plugin tables for entries containing script tags, iframe tags, or event handlers (onerror, onload, onclick). Use: SELECT * FROM wp_postmeta WHERE meta_value LIKE '%<script%';
    Affected if Database contains stored XSS payloads in plugin-related meta fields.
  5. Review admin user accounts for unauthorized additions
    Go to Users > All Users in WordPress admin and check for unexpected administrator accounts created without your knowledge.
    Affected if New admin accounts exist that you did not create.

You are affected if the Find Your Reps plugin version 1.2 or below is installed and active, and the plugin's form submission feature is enabled on your site.

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 version of the Find Your Reps plugin when available; if no patch exists, disable the plugin. Implement anti-CSRF tokens on all state-changing form actions and ensure proper input sanitization and output encoding.

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

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 locally
dbcve dependency scanner

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