CVE-2025-7685
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 · uneditedThe Like & Share My Site plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 0.2. This is due to missing or incorrect nonce validation on the 'lsms_admin' 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 confidenceThe Like & Share My Site WordPress plugin fails to validate nonces on the 'lsms_admin' admin page, allowing unauthenticated attackers to forge requests that modify plugin settings. By tricking administrators into clicking malicious links, attackers can inject malicious web scripts or alter configuration.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify plugin installationCheck wp-content/plugins/ for 'like-and-share-my-site' or 'like-share-my-site' folder, or query WordPress plugins tableAffected if Plugin folder or database entry exists
-
Identify installed versionRead version from plugin header in main PHP file or compare against WordPress plugin repository releasesAffected if Installed version lacks the nonce validation fix (check plugin changelog for security patches)
-
Locate lsms_admin admin pageAccess WordPress admin under the plugin menu or inspect plugin code for 'lsms_admin' page handlerAffected if The lsms_admin page exists and handles form submissions
-
Check nonce validation in form handlingInspect plugin PHP code for form action handlers on lsms_admin page; look for wp_verify_nonce or check_admin_referer calls before processing settingsAffected if Form processing lacks nonce verification (nonce check missing or commented out)
-
Test settings modificationSubmit a settings change request to lsms_admin page with invalid/missing nonce parameter and observe if the change is acceptedAffected if Settings are saved without requiring a valid nonce token
Environment is affected if the Like & Share My Site plugin is installed and the lsms_admin page processes settings changes without validating nonce tokens.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply vendor patch when available; until then, remove the plugin or implement manual nonce validation on the lsms_admin form actions.
Update to Like & Share My Site version 0.3 or later
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate the 'Like & Share My Site' plugin
- Check if an update is available and update to the latest version (version 0.3 or higher)
- Verify the update was applied successfully
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2025-7685 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-7685 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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