CVE-2025-67993
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 Vito Peleg Atarim atarim-visual-collaboration allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Atarim: from n/a through <= 4.2.1.
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 Atarim visual collaboration plugin allows exploitation of incorrectly configured access control security levels, potentially enabling unauthorized users to access privileged functionality or perform actions beyond their designated security level.
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.
-
Confirm Atarim plugin is installedCheck your site's plugin/module list or codebase for the Atarim visual collaboration plugin presence. Look for atarim-related files, folders, or package dependencies.Affected if Atarim plugin is not found in the environment, then this CVE does not apply
-
Identify installed Atarim versionLocate the version information in the plugin's metadata file (such as package.json, plugin.xml, composer.json, or a VERSION file within the Atarim installation directory). Compare it against the affected range (versions up to and including 4.2.1).Affected if The installed version is 4.2.1 or lower, placing it within the affected range
-
Examine access control security level configurationInspect the Atarim configuration files (commonly found in config/settings files, a security config file, or the plugin admin panel) for the access control or security level settings. Verify what security levels are defined and how they are assigned to users or roles.Affected if Security levels are defined but allow roles with lower privileges to access higher-privilege actions, or if no role-based restrictions are enforced on sensitive operations
-
Test for proper authorization enforcementAttempt to perform actions that should require elevated privileges (such as editing collaborative content, managing users, or accessing admin functions) using an account with lower security permissions. Check if the application rejects the request or permits the action.Affected if Actions that should be restricted are successfully performed by users lacking the required security level, indicating the authorization check is missing or flawed
If Atarim is installed with version 4.2.1 or lower AND the access control security levels are misconfigured or fail to enforce proper authorization, the environment is affected by this vulnerability.
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 in Atarim, implement proper authorization checks for all sensitive operations, and upgrade to a version beyond 4.2.1 if available.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-67993 — 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-67993 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