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

CVE-2026-57785

HIGH · 8.8 CVSS v3.1 Published 2026-07-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges 4 weeks old

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
Unauthenticated Cross Site Request Forgery (CSRF) in ApusListing <= 1.2.63 versions.

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

An unauthenticated Cross Site Request Forgery (CSRF) vulnerability exists in ApusListing plugin/theme versions 1.2.63 and below. Attackers can trick authenticated users into submitting malicious requests without their consent, potentially allowing unauthorized actions such as modifying listings or configurations.

MitigationUpdate ApusListing to the latest version > 1.2.63 which should contain CSRF token validation. If no patch is available, consider disabling the plugin until a fix is released.

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/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. Verify ApusListing is installed
    Check WordPress plugins directory for 'apuslisting' folder or check wp-admin > Plugins for ApusListing
    Affected if ApusListing plugin or theme is present in the WordPress installation
  2. Check installed version
    Look at the plugin version in header comment of main plugin file (apuslisting.php) or in WordPress admin plugin list
    Affected if Version is 1.2.63 or lower
  3. Inspect for anti-CSRF nonce implementation
    Search plugin source code for 'wp_nonce_field', 'wp_nonce_url', 'check_admin_referer', or 'check_ajax_referer' calls on forms/actions that modify settings, create listings, or handle user roles
    Affected if No nonce verification found on state-changing actions or nonce checks are missing entirely
  4. Verify SameSite cookie attributes
    Inspect HTTP response headers for session cookies (wp-settings, wordpress_logged_in) and check if SameSite attribute is present and set to 'Lax' or 'Strict'
    Affected if SameSite attribute is missing or set to 'None' on session cookies

You are affected if ApusListing version 1.2.63 or below is installed and lacks nonce token validation on administrative actions.

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 ApusListing to the latest version > 1.2.63 which should contain CSRF token validation. If no patch is available, consider disabling the plugin until a fix is released.

Have this fixed 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 help mitigating

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-2026-57785 — 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-2026-57785 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