LiveActive security incident?Get immediate response
CVE Record

CVE-2026-32447: WordPress Atarim plugin <= 4.3.2 - Broken Access Control vulnerability

Missing 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.3.2.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-32447 affects the WordPress Atarim plugin through version 4.3.2. It is a broken access control issue that may let a logged-in user perform actions they should not be authorized to perform. The public record rates it medium severity, with limited integrity impact and no stated confidentiality or availability impact.

Executive priority

Treat as a moderate-priority WordPress exposure. It is not described as remotely exploitable without login, but it can undermine workflow integrity where many users have accounts. Prioritize internet-facing or client-accessible WordPress sites using Atarim.

Technical view

The issue is CWE-862 Missing Authorization in Vito Peleg Atarim, package atarim-visual-collaboration, affecting versions up to and including 4.3.2. CVSS 3.1 is 4.3: network-accessible, low complexity, low privileges required, no user interaction, unchanged scope, low integrity impact only.

Likely exposure

Exposure is most relevant to WordPress sites with the Atarim visual collaboration plugin installed at version 4.3.2 or earlier. Because exploitation requires low privileges, sites allowing many subscriber, contributor, client, or project-user accounts may have higher practical risk.

Exploitation context

The provided sources do not report active exploitation, and the CVE is not marked as CISA KEV. Public details are limited to the vulnerability class and scoring, so the exact unauthorized action is not confirmed in the supplied material.

Researcher notes

Public information is sparse. The CVE identifies missing authorization and CVSS characteristics but not the affected endpoint, capability boundary, or fixed version. Avoid assuming exploitability beyond authenticated integrity impact unless vendor or researcher details emerge.

Mitigation direction

  • Inventory WordPress sites for the Atarim plugin and installed version.
  • If version is 4.3.2 or earlier, check vendor or Patchstack guidance for a fixed release.
  • Update the plugin if a vendor-supported patched version is available.
  • Limit WordPress accounts to users with a current business need.
  • Review plugin-related roles and permissions for least privilege.
  • Consider disabling the plugin where it is not business-critical until guidance is available.

Validation and detection

  • Confirm whether atarim-visual-collaboration is installed on each WordPress site.
  • Record the plugin version and flag versions 4.3.2 or earlier.
  • Review user roles with access to Atarim or WordPress project workflows.
  • Check vendor, CVE, and Patchstack pages for updated remediation details.
  • Monitor logs for unusual actions by low-privileged authenticated users.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-32447 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2026-32447Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Vito PelegAtarimatarim-visual-collaboration, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.