LiveActive security incident?Get immediate response
CVE Record

CVE-2023-46606: WordPress AtomChat plugin <= 1.1.4 - Broken Access Control vulnerability

Missing Authorization vulnerability in Team AtomChat AtomChat atomchat allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects AtomChat: from n/a through <= 1.1.4.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-46606 is a broken access control issue in the WordPress AtomChat plugin through version 1.1.4. An unauthenticated remote attacker may access information that should require authorization. The available sources rate it medium severity, with limited confidentiality impact and no integrity or availability impact stated.

Executive priority

Prioritize routine but prompt triage for public WordPress sites using AtomChat. This is not evidenced as actively exploited, but unauthenticated access control flaws can expose data and are inexpensive for attackers to probe at scale.

Technical view

The CVE describes missing authorization in Team AtomChat's AtomChat WordPress plugin, mapped to CWE-862. CVSS 3.1 is 5.3: network reachable, low complexity, no privileges, no user interaction, unchanged scope, low confidentiality impact, and no integrity or availability impact.

Likely exposure

Exposure is likely limited to WordPress sites running the AtomChat plugin at version 1.1.4 or earlier. The bundle does not identify specific vulnerable endpoints, required configurations, or a fixed version.

Exploitation context

The source bundle does not show CISA KEV listing or cited active exploitation. Because the vector is unauthenticated and network-accessible, internet-facing WordPress sites should still treat confirmed vulnerable installations as externally reachable information-exposure risk.

Researcher notes

Evidence is limited to the CVE summary and Patchstack database reference. The bundle does not provide affected endpoint details, exploit examples, proof of active exploitation, or a named patched version. Avoid assuming more than low confidentiality impact unless vendor details expand the scope.

Mitigation direction

  • Inventory WordPress sites for AtomChat plugin version 1.1.4 or earlier.
  • Check AtomChat and Patchstack guidance for a fixed release or vendor mitigation.
  • Update only to a vendor-confirmed fixed version when available.
  • Disable or remove AtomChat where business need is low until guidance is confirmed.
  • Limit access to WordPress administrative surfaces using existing controls.

Validation and detection

  • Confirm installed AtomChat versions across production and staging WordPress sites.
  • Review user-role access to AtomChat features for unintended unauthenticated visibility.
  • Check web logs for unusual requests to AtomChat-related paths.
  • Monitor the CVE and Patchstack entry for fixed-version details.
  • Retest after any plugin update or temporary disablement.
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-2023-46606 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
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2023-46606Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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
Team AtomChatAtomChatatomchat, 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.