ZDF
Sign inSign up

Vulnerabilities

Vulnerability · GHSA-hpgx-8qg3-5w7v

Field-level security bypass for email address field via meeting's attendees endpoint

Published Aug 29, 2026 · catalog updated Sep 15, 2026 · Field-level security bypass for

Last checked Nov 1, 2026. A connected source was read within the last 7 days.

Open the advisory

Exploitation likelihood is not on this record for GHSA-hpgx-8qg3-5w7v. A missing EPSS score is not a low risk. Compare Field-level security bypass for with the linked advisory before you change production.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Field-level security bypass for).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
Low—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Version ranges on file
Affected products
php EspoCRM

The impact is low. It is rare that a user who has access to a meeting should not have access to ## Summary EspoCRM exposes attendee lists for meetings and calls through authenticated helper endpoints. The helper fetches related users, contacts, and leads with their column selected. It then tries to mask hidden attendee emails — but the masking check uses the parent event scope ( or ) instead of the attendee entity's own scope ( , , or ). A user explicitly forbidden from reading can still recover hidden attendee emails through the meeting or call attendees helper, because the ACL check is performed against the wrong entity type. ## Notes Impact is very low. Users who already have access to the meeting and have access to the attendee record by default have access to the email address. It is a rare case that access to the email address will be restricted. ## Reporter **Yash Shendge (ashrexon)** 2026-07-22

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • php EspoCRM<=10.0.3

How to fix GHSA-hpgx-8qg3-5w7v

  • Upgrade

    GHSA-hpgx-8qg3-5w7v lists a fix boundary at 10.0.3. Compare the installed build with that boundary before you change production.

  • Version check

    Affected <=10.0.3

  • Advisory

    Open the inventory_github record and follow its fix.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for GHSA-hpgx-8qg3-5w7v. A missing EPSS score is not a low risk. Compare Field-level security bypass for with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with EspoCRM <=10.0.3. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-863: Incorrect Authorization. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

EspoCRM security

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Aug 29, 2026 · Maintainer security tabs

    Detected

    The impact is low. It is rare that a user who has access to a meeting should not have access to ## Summary EspoCRM exposes attendee lists for meetings and calls through authenticated helper endpoints. The helper fetches related users, contacts, and leads with their column selected. It then tries to mask hidden attendee emails — but the masking check uses the parent event scope ( or ) instead of th

  2. Sep 15, 2026 · Maintainer security tabs

    Updated

    The impact is low. It is rare that a user who has access to a meeting should not have access to ## Summary EspoCRM exposes attendee lists for meetings and calls through authenticated helper endpoints. The helper fetches related users, contacts, and leads with their column selected. It then tries to mask hidden attendee emails — but the masking check uses the parent event scope ( or ) instead of th

Sources

  • Maintainer security tabsVendor advisoryGHSA-hpgx-8qg3-5w7v

    The impact is low. It is rare that a user who has access to a meeting should not have access to ## Summary EspoCRM exposes attendee lists for meetings and calls through authenticated helper endpoints. The helper fetches related users, contacts, and leads with their column selected. It then tries to mask hidden attendee emails — but the masking check uses the parent event scope ( or ) instead of th

    github.com

Freshness

Last verified in this catalog Sep 15, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • Maintainer security tabsNov 1, 2026