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

CVE-2025-7687

MEDIUM · 6.1 CVSS v3.1 Published 2025-07-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
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
The Latest Post Accordian Slider plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.3. This is due to missing or incorrect nonce validation on the 'lpaccordian' page. This makes it possible for unauthenticated attackers to update settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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 · high confidence

The Latest Post Accordion Slider plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to 1.3 due to missing or incorrect nonce validation on the 'lpaccordian' admin page. This allows unauthenticated attackers to forge administrative requests that can modify plugin settings and inject malicious scripts, provided they can trick a site administrator into clicking a malicious link.

MitigationUpdate to the latest version of the plugin when a patch is released. If no patch is available, consider removing the plugin. Administrators should also be educated about not clicking untrusted links to reduce CSRF attack surface.

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
None

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

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. Locate the plugin in your WordPress installation
    Navigate to your WordPress wp-content/plugins/ directory and search for a folder named 'latest-post-accordion-slider', 'latest-post-accordion', or similar containing 'accordion' and 'slider' in the name. Alternatively, log into WordPress admin and go to Plugins > Installed Plugins to find the plugin.
    Affected if The plugin is found installed in the WordPress environment
  2. Identify the installed version number
    If accessing via file system, open the main plugin PHP file (usually named similarly to the plugin folder) and look for a version comment or 'Version:' header in the file header. If via WordPress admin, the version is displayed in the Plugins list.
    Affected if The version displayed is 1.3 or lower (any version 'up to and including 1.3')
  3. Verify the lpaccordian admin page exists
    In WordPress admin, navigate to the plugin settings page. Look for a menu item labeled 'lpaccordian' or a page under the plugin's admin menu that handles its settings. Check the URL for 'lpaccordian' as a parameter or path.
    Affected if The lpaccordian admin settings page is accessible in the WordPress admin dashboard
  4. Confirm the admin page handles settings without nonce verification (code review)
    If you have access to the plugin source code, examine the PHP file that handles the lpaccordian admin page requests. Look for the presence of 'wp_verify_nonce' or 'check_admin_referer' functions in the form processing code that handles settings updates.
    Affected if The code handling the lpaccordian admin page settings save requests does not contain nonce validation checks, or contains incorrect/improper nonce validation

Your environment is affected if the Latest Post Accordion Slider plugin is installed with version 1.3 or lower and the lpaccordian admin settings page exists without proper nonce validation.

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 plugin when a patch is released. If no patch is available, consider removing the plugin. Administrators should also be educated about not clicking untrusted links to reduce CSRF attack surface.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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