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

CVE-2025-22658

HIGH · 7.1 CVSS v3.1 Published 2025-03-27
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 Listings for Appfolio Listings for Appfolio listings-for-appfolio allows Stored XSS.This issue affects Listings for Appfolio: from n/a through <= 1.2.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

Cross-Site Request Forgery (CSRF) vulnerability in the Listings for Appfolio WordPress plugin (versions <= 1.2.0) allows authenticated attackers to inject malicious JavaScript through stored XSS by tricking administrators into submitting crafted requests.

MitigationUpdate Listings for Appfolio to the latest version and implement anti-CSRF tokens on all state-changing forms.

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 Listings for Appfolio plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Listings for Appfolio' in the list
    Affected if Plugin is not found in the installed plugins list
  2. Check if the plugin is active
    In Plugins > Installed Plugins, verify the 'Listings for Appfolio' plugin has an 'Active' status indicator
    Affected if Plugin is not active - vulnerability cannot be exploited
  3. Determine installed plugin version
    Click on the plugin name in the plugins list to view details, or check the plugin header in /wp-content/plugins/listings-for-appfolio/listings-for-appfolio.php for the 'Version' field
    Affected if Version cannot be determined or is <= 1.2.0
  4. Compare version to affected range
    Compare the installed version number to the affected range: any version <= 1.2.0 is vulnerable
    Affected if Installed version is 1.2.0 or lower

If the Listings for Appfolio plugin is active and the installed version is 1.2.0 or lower, the environment is affected by this CSRF/stored XSS vulnerability

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Listings for Appfolio to the latest version and implement anti-CSRF tokens on all state-changing forms.

Recommended fix Moderate confidence

Latest available version (likely 1.2.1 or higher)

  1. 1. Log in to your WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Listings for Appfolio' plugin
  4. 4. Check if an update is available and update to the latest version
  5. 5. Verify the update was successful

Generated from the published advisory — verify against the referenced sources before acting.

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-22658 — 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-22658 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