dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2025-60195

CRITICAL · 9.8 CVSS v3.1 Published 2025-11-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Incorrect Privilege Assignment vulnerability in Vito Peleg Atarim atarim-visual-collaboration allows Privilege Escalation.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 confidence

A privilege escalation vulnerability exists in Atarim visual collaboration software due to incorrect privilege assignment. The flaw allows authenticated users to elevate their permissions beyond what they should normally have access to, potentially gaining administrative or higher-privileged system access.

MitigationUpgrade to a version beyond 4.2.1 once available. Until then, restrict user permissions to the minimum required and monitor for unauthorized privilege escalation attempts.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Atarim installation and version
    Locate the Atarim installation directory and check the version file or binary (common locations: /opt/atarim, /usr/local/atarim, or check running services). Use commands like 'dpkg -l atarim', 'rpm -qa atarim', or inspect the application's About/Version page if a web interface exists.
    Affected if The installed version is 4.2.1 or lower, or version cannot be determined but the software is present.
  2. Verify authentication configuration
    Examine the authentication configuration files (typically in conf/ or config/ directories under the installation path). Look for settings related to user authentication, session management, and role-based access control (RBAC) definitions.
    Affected if Authentication is enabled and users can log in to the Atarim system.
  3. Review user role assignments
    Inspect the user database, directory, or configuration where user roles are stored. Check for any misconfigured role mappings that could allow a standard authenticated user to be assigned administrative privileges.
    Affected if Standard or non-admin user accounts exist in the system and can log in.
  4. Check privilege escalation paths
    Review the authorization logic or access control policies. Look for API endpoints, functions, or features that handle permission elevation or role changes. Examine logs for any privilege modification events.
    Affected if The system contains features that handle role or permission changes, even if not explicitly configured.
  5. Audit admin access and permissions
    Query or inspect the current set of users with administrative privileges. Compare the expected admin count against actual admin accounts in the system. Check for any unexpected admin-level accounts.
    Affected if There are multiple user accounts in the system beyond a single admin.

You are affected if Atarim visual collaboration software is installed and any authenticated user account can elevate permissions beyond their assigned role, particularly if the installed version is 4.2.1 or lower.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a version beyond 4.2.1 once available. Until then, restrict user permissions to the minimum required and monitor for unauthorized privilege escalation attempts.

Recommended fix Moderate confidence

4.2.2 or latest available version

  1. 1. Backup your WordPress site and database before performing any updates.
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
  3. 3. Locate the Atarim (atarim-visual-collaboration) plugin.
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version.
  5. 5. Alternatively, download the updated plugin version from the official WordPress plugin repository or vendor site.
  6. 6. After updating, verify the plugin is functioning correctly on your site.
  7. 7. Test that user privilege assignments work correctly to confirm the vulnerability is remediated.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-60195 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-60195 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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