LiveActive security incident?Get immediate response
CVE Record

CVE-2023-43336: Sangoma Technologies FreePBX before cdr 15.0.18, 16.0.40, 15.0.16, and 16.0.17 was discovered to contain an...

Sangoma Technologies FreePBX before cdr 15.0.18, 16.0.40, 15.0.16, and 16.0.17 was discovered to contain an access control issue via a modified parameter value, e.g., changing extension=self to extension=101.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is an access-control weakness in Sangoma FreePBX CDR. A user may be able to change a request parameter and view data tied to another extension. That creates confidentiality and privacy risk for call records, but the public bundle does not provide CVSS, exploit maturity, or full affected-version detail.

Executive priority

Treat as a targeted privacy and records-access issue, not a confirmed emergency. Prioritize patching where FreePBX stores sensitive call metadata or where many users have CDR portal access.

Technical view

CVE-2023-43336 is reported as CWE-284 in FreePBX CDR before the cited CDR releases. The issue is parameter tampering that bypasses intended extension-level access control. The source bundle describes unauthorized access by changing an extension selector, but does not include exploit prerequisites, authentication requirements, or vendor advisory detail.

Likely exposure

Most relevant to organizations running Sangoma FreePBX with the CDR module below the cited release levels. Exposure depends on whether users can access CDR views and whether extension-level segregation is relied on for privacy or compliance.

Exploitation context

The bundle does not cite active exploitation, and KEV is false. Public disclosure exists, but the provided sources do not establish exploitation in the wild, exploit availability, or unauthenticated reachability.

Researcher notes

Evidence is limited to the CVE description and linked disclosure. The CVE metadata has no CVSS vector and generic affected-product fields. Verify exact module branches, fixed versions, and authentication assumptions from Sangoma before assigning final risk.

Mitigation direction

  • Check Sangoma FreePBX and CDR module versions against the cited fixed release levels.
  • Upgrade FreePBX CDR to current vendor-supported releases where applicable.
  • Review Sangoma guidance for exact affected branches and remediation instructions.
  • Restrict CDR access to users with a business need until patched.
  • Audit CDR access logs for unusual cross-extension record access.

Validation and detection

  • Inventory FreePBX systems and installed CDR module versions.
  • Confirm whether CDR users are limited to their own extension data.
  • Review role and permission assignments for CDR access.
  • Check logs for anomalous CDR queries involving other extensions.
  • Track remediation evidence with version screenshots or package records.
Prepared
Confidence
medium
Sources
4

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-284: 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-43336 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

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

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

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

CWE-284 · source CWE mapping

Improper Access Control

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