Cvent Registration · Vulnerability Disclosure

Cvent Registration Vulnerability Disclosure

Vulnerability disclosure

Cvent runs a published Vulnerability Disclosure Program with a stated research scope, stated out-of-bounds activities, a submission form, and a commitment to acknowledge each report. It is NOT advertised at /.well-known/security.txt — every host returns 404 for that path (see well-known/cvent-registration-well-known.yml) — so the programme is discoverable only through cvent.com and the trust center.

Cvent Registration publishes a vulnerability disclosure policy for reporting security issues.

Attendee ManagementAttendeesConferencesEvent ManagementEventAuthenticationOn-Site Check-InPaymentsRegistrationREST APISCIMSDKsSOAPTicketingWebhook

Program:

Disclosure Policy

Policy

confidentialityCvent requires that reported vulnerabilities be kept confidential and not publicly disclosed, and that the finding not have been previously reported.

Policy

out_of_scopeAny attempt to modify or delete dataAccessing, downloading or modifying accounts and data that do not belong to youDenial of service (DoS/DDoS) testingSending unsolicited or unauthorized email, spam or other unsolicited messagesTesting third-party websites, applications or services that integrate with CventPosting, transmitting, uploading, linking to or storing malware or similar harmful softwareAny activity that violates applicable law

Policy

response_commitment"The Cvent Security team will acknowledge receipt of each reported vulnerability, conduct a thorough investigation, and then take appropriate action for resolution."

Policy

scopeCvent services and products to which the researcher has authorized access.

Security Contact

Source

Vulnerability Disclosure

generated: '2026-09-07'
method: searched
source: https://www.cvent.com/en/event-management-software/vulnerability-disclosure-program
description: >-
  Cvent runs a published Vulnerability Disclosure Program with a stated research scope, stated
  out-of-bounds activities, a submission form, and a commitment to acknowledge each report. It is
  NOT advertised at /.well-known/security.txt — every host returns 404 for that path (see
  well-known/cvent-registration-well-known.yml) — so the programme is discoverable only through
  cvent.com and the trust center.
program:
  name: Cvent Vulnerability Disclosure Program
  url: https://www.cvent.com/en/event-management-software/vulnerability-disclosure-program
  http_status: 200
  verified: '2026-09-07'
  type: vulnerability-disclosure
  bug_bounty: false
  platform: null
  submission: Web form ("Report a Vulnerability") on the programme page
  contact_email: null
  security_txt: false
  pgp_key: false
  safe_harbor_stated: false
policy:
  confidentiality: >-
    Cvent requires that reported vulnerabilities be kept confidential and not publicly disclosed,
    and that the finding not have been previously reported.
  response_commitment: >-
    "The Cvent Security team will acknowledge receipt of each reported vulnerability, conduct a
    thorough investigation, and then take appropriate action for resolution."
  scope: Cvent services and products to which the researcher has authorized access.
  out_of_scope:
    - Any attempt to modify or delete data
    - Accessing, downloading or modifying accounts and data that do not belong to you
    - Denial of service (DoS/DDoS) testing
    - Sending unsolicited or unauthorized email, spam or other unsolicited messages
    - Testing third-party websites, applications or services that integrate with Cvent
    - Posting, transmitting, uploading, linking to or storing malware or similar harmful software
    - Any activity that violates applicable law
trust_center:
  url: https://trust.cvent.com/
  indicator: >-
    The trust center's "Has a bug bounty or vulnerability disclosure program" indicator links to
    this same programme page.

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this

find_securityBrowse and filter every security artifact in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This security artifact

curl "https://apis.io/api/v1/security/cvent-registration-vulnerability-disclosure"

All security posture

curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.