CVE-2026-24590
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 VideoWhisper.Com Paid Videochat Turnkey Site allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects Paid Videochat Turnkey Site: from n/a through 7.3.23.
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 VideoWhisper Paid Videochat Turnkey Site allows attackers to exploit incorrectly configured access control security levels, potentially bypassing proper authentication or authorization checks to access restricted functionality or data.
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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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.
-
Confirm VideoWhisper Paid Videochat installationLocate the Paid Videochat Turnkey Site installation directory and identify the software version file (typically version.php, info.php, or a similar file in the root or includes directory).Affected if The installed version is 7.3.23 or any earlier version of the Paid Videochat Turnkey Site.
-
Identify access control security level configurationSearch for configuration files related to access control, security levels, or user roles (commonly in config.php, settings.php, or a security/permissions subdirectory). Look for settings named security_level, access_control, or similar that control user privileges.Affected if A misconfigured security level setting exists that allows elevated access without proper authorization enforcement.
-
Verify authorization enforcement on privileged functionsTest access to administrative functions, user management pages, or sensitive features by accessing them directly without authentication or with a low-privilege account. Common endpoints include admin/, manage/, or user management modules.Affected if Access is granted to functionality that should require higher privileges or authentication.
-
Inspect role-based access control implementationExamine the codebase for role verification logic before executing privileged operations. Look for missing role checks in PHP files that handle user data, payments, or site administration.Affected if The application lacks proper role-based authorization checks at access points.
Your environment is affected if the VideoWhisper Paid Videochat Turnkey Site version is 7.3.23 or earlier AND the access control security level settings are misconfigured to allow unauthorized access to privileged functions.
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 dataReview and properly configure access control security levels across the application, implement proper authorization checks for all sensitive operations, and ensure role-based access controls are correctly enforced.
- 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-2026-24590 — 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-2026-24590 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