Cvent Community · Vulnerability Disclosure

Cvent Community Vulnerability Disclosure

Vulnerability disclosure

Cvent Community publishes a vulnerability disclosure policy for reporting security issues. A dedicated security contact is published.

CertificationCommunityCustomer-SupportCvent AcademyEducationForumsKnowledge BaseLearning CentersSoftware-as-a-ServiceTraining
Program:

Disclosure Policy

Policy

Security Contact

Contact
security@cvent.com

Source

Vulnerability Disclosure

cvent-community-vulnerability-disclosure.yml Raw ↑
generated: '2026-09-07'
method: searched
probe: true
source: >-
  https://www.cvent.com/en/event-management-software/vulnerability-disclosure-program (HTTP 200,
  fetched 2026-09-07); https://www.cvent.com/en/event-management-software/report-security-vulnerability
  (HTTP 200); https://trust.cvent.com/ (HTTP 200)
program:
  published: true
  name: Cvent Vulnerability Disclosure Program
  url: https://www.cvent.com/en/event-management-software/vulnerability-disclosure-program
  report_form: https://www.cvent.com/en/event-management-software/report-security-vulnerability
  contact_email: security@cvent.com
  bug_bounty: false
  rewards: false
  platform: null
  scope_note: >-
    The program is published by Cvent for the Cvent estate, which includes the community.cvent.com and
    support.cvent.com hosts this record covers. It is not a Cvent-Community-specific policy.
policy:
  - https://www.cvent.com/en/event-management-software/vulnerability-disclosure-program
contact:
  - security@cvent.com
security_txt:
  served: false
  probed:
    - https://community.cvent.com/.well-known/security.txt
    - https://support.cvent.com/.well-known/security.txt
    - https://release.cvent.com/.well-known/security.txt
    - https://status.cvent.com/.well-known/security.txt
    - https://www.cvent.com/.well-known/security.txt
    - https://cvent.com/.well-known/security.txt
  note: >-
    No RFC 9116 file on any host. community.cvent.com answers 200 with its HTML catch-all shell,
    support.cvent.com answers 401, and the rest 404. An automated scanner finds nothing at the
    machine-readable path even though a disclosure program exists.
evidence:
  - source: https://www.cvent.com/en/event-management-software/vulnerability-disclosure-program
    kind: disclosure-policy
    http_status: 200
  - source: https://www.cvent.com/en/event-management-software/report-security-vulnerability
    kind: report-form
    http_status: 200
  - source: https://trust.cvent.com/
    kind: trust-center
    http_status: 200

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-community-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.

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