Empowerly · Vulnerability Disclosure

Empowerly Vulnerability Disclosure

Vulnerability disclosure

Empowerly runs a coordinated vulnerability disclosure program on Hackerone. A dedicated security contact is published.

CompanyEducationEdTechCollege AdmissionsCounselingStudentsCareer ServicesConsumer ServicesStatus Page
Program: Hackerone

Disclosure Policy

Security Contact

Contact
{"published_purpose" => "SOC 2 report requests (no stated vulnerability-intake purpose)", "source" => "https://empowerly.com/security", "type" => "email", "value" => "security@empowerly.com"}

Source

Vulnerability Disclosure

Raw ↑ 
generated: '2026-08-12'
method: searched
probe: true
source: https://empowerly.com/security
program:
  formal_vdp: false
  bug_bounty: false
  safe_harbor: null
  note: >-
    Empowerly publishes NO formal vulnerability disclosure policy, no responsible-disclosure page,
    no safe-harbor language, and no bug bounty. /responsible-disclosure and /vulnerability-disclosure
    both 404, and /.well-known/security.txt is not served (the S3 origin answers 403 AccessDenied for
    the path, which is an absence rather than a gate). What DOES exist is a reachable security
    contact address published on the security commitments page, alongside a statement that
    vulnerabilities are patched by severity. A researcher has somewhere to send a report; they have
    no published policy, scope, or disclosure timeline to rely on.
contact:
- type: email
  value: security@empowerly.com
  source: https://empowerly.com/security
  published_purpose: SOC 2 report requests (no stated vulnerability-intake purpose)
security_txt:
  served: false
  probed:
  - url: https://empowerly.com/.well-known/security.txt
    http_status: 403
    note: S3 AccessDenied XML — no document served
  - url: https://api.empowerly.com/.well-known/security.txt
    http_status: 403
bounty_platforms_checked:
- platform: HackerOne
  found: false
- platform: Bugcrowd
  found: false
- platform: Intigriti
  found: false
evidence:
- url: https://empowerly.com/security
  http_status: 200
  fetched: '2026-08-12'
- url: https://empowerly.com/responsible-disclosure
  http_status: 404
- url: https://empowerly.com/vulnerability-disclosure
  http_status: 404
- url: https://empowerly.com/.well-known/security.txt
  http_status: 403
recommendation: >-
  Serving an RFC 9116 /.well-known/security.txt naming security@empowerly.com, plus a one-page
  disclosure policy with scope and safe harbor, would convert an implicit contact into a real
  program at near-zero cost.

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/empowerly-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.