CVE-2025-68568
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 · uneditedMissing Authorization vulnerability in Claspo Popup Builders Claspo – Popups, Spin the Wheel & Email Capture claspo allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Claspo – Popups, Spin the Wheel & Email Capture: from n/a through <= 1.0.7.
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 confidenceThe Claspo WordPress plugin (versions <= 1.0.7) contains a missing authorization vulnerability that allows unauthenticated attackers to exploit incorrectly configured access control security levels. This broken access control issue permits unauthorized access to certain plugin functionality that should require proper authentication and authorization checks.
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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 Claspo plugin is installedNavigate to WordPress admin dashboard under Plugins > Installed Plugins and look for 'Claspo', or check the /wp-content/plugins/ directory for a folder named 'claspo' or similar.Affected if The Claspo plugin appears in the installed plugins list or its folder exists in the plugins directory.
-
Determine installed Claspo plugin versionIn WordPress admin, click on the Claspo plugin to view its details and note the version number displayed. Alternatively, open the main plugin file (e.g., claspo.php) in a text editor and look for the 'Version:' header in the plugin comment block.Affected if The version listed is 1.0.7 or lower.
-
Confirm the broken access control vulnerability existsUsing a tool like curl or Burp Suite, send a request to common Claspo plugin AJAX endpoints (such as /wp-admin/admin-ajax.php?action=claspo_*) or direct PHP files in the /wp-content/plugins/claspo/ directory WITHOUT providing any authentication cookies or credentials.Affected if The server returns a successful HTTP response (200 OK) with data or performs the requested action instead of returning a 401 Unauthorized or 403 Forbidden error.
-
Check for unauthorized data access or modificationReview server access logs for any requests to Claspo plugin endpoints originating from IP addresses that are not authenticated WordPress users, looking for successful responses.Affected if Requests to protected Claspo functionality succeed without valid authentication tokens.
If the Claspo plugin version is 1.0.7 or lower and its endpoints are accessible without authentication, the environment is affected by this CVE.
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.
From vendor dataApply vendor-supplied patch or update to the latest version of the Claspo plugin once available. If no patch exists, restrict access to the affected plugin endpoints at the web server level until a fix is released.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-68568 — 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-68568 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