CVE-2025-68564
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 sendy Sendy sendy allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Sendy: from n/a through <= 3.4.2.
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 confidenceMissing Authorization vulnerability in Sendy email marketing software allows exploiting incorrectly configured access control security levels. Unauthenticated or unauthorized users may access functionality they should not have permission to use due to missing 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
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Sendy installation and versionLocate the Sendy installation directory and check for a version file or changelog. Common paths include /var/www/html/sendy or similar web root locations. Look for a version.php file or check the admin dashboard for version information.Affected if Sendy is installed and running without documented security patches applied
-
Inspect sensitive endpoint access controlsReview the source code of Sendy's admin functionality (typically in PHP files in the includes/ or functions/ directories). Examine endpoints that handle user management, campaign creation, list management, and settings for the presence of authorization check functions at the start of each file.Affected if Sensitive PHP files lack authorization validation routines at the beginning
-
Verify authentication enforcement on admin routesCheck the routing or entry point files (such as index.php or .htaccess rules) to confirm that admin pages require valid session authentication. Look for code that allows unauthenticated access to paths like /admin/, /subscribers/, or /campaigns/.Affected if Admin routes can be accessed without providing valid credentials
-
Test for unauthenticated access to privileged functionsUsing a browser or HTTP tool, attempt to access Sendy admin URLs directly without logging in. Try accessing common admin endpoints such as the dashboard, user management, or settings pages while logged out.Affected if Privileged pages load or return successful responses without authentication credentials
-
Review role-based access control configurationExamine the database or configuration files for user role definitions and permission settings. Check if there are defined security levels and whether the application enforces them consistently across all functionality.Affected if No role or permission enforcement exists, or security levels are defined but not checked in the code
A user is affected if Sendy is installed and sensitive endpoints or admin functionality can be accessed without proper authentication or authorization validation.
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 dataImplement proper authorization checks across all sensitive endpoints and enforce role-based access control (RBAC) to ensure users can only access resources and actions permitted for their security level.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-68564 — 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-68564 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