Moosend · Vulnerability Disclosure

Moosend Vulnerability Disclosure

Vulnerability disclosure

Moosend runs a coordinated vulnerability disclosure program on Bugcrowd.

Email MarketingMarketing AutomationCampaignsMailing ListsSubscribersTransactional EmailSMTPSegmentationAnalyticsEmailNewslettersLanding PagesWebsite TrackingMarketing
Program: Bugcrowd

Disclosure Policy

Policy

Security Contact

Source

Vulnerability Disclosure

Raw ↑
generated: '2026-08-13'
method: searched
probe: true
source: https://moosend.com/privacy-policy/disclosure/
policy:
  - https://moosend.com/privacy-policy/disclosure/
submission_form:
  - https://moosend.com/disclosure/
contact: []
contact_note: >-
  No security@ address is published. Reports are submitted through a web form at
  https://moosend.com/disclosure/, which forwards to Bugcrowd.

programme:
  type: vulnerability-disclosure-programme
  platform: Bugcrowd
  bug_bounty: false
  rewards: >-
    Explicitly not a bug bounty. Researchers receive Bugcrowd points for validly
    accepted reports; there is no monetary reward. "Moosend reserves the right to
    accept or reject any submission."
  severity_taxonomy: Bugcrowd Vulnerability Rating Taxonomy (VRT)
  safe_harbor: true
  safe_harbor_quote: >-
    Research conducted in accordance with the policy is "Authorized in accordance
    with the Computer Fraud and Abuse Act (CFAA)", "Exempt from the Digital
    Millennium Copyright Act (DMCA)", "Exempt from restrictions in our Terms of
    Service", and "Lawful, helpful to the overall security of the Internet, and
    conducted in good faith."
  out_of_scope:
    - CSRF on anonymous forms
    - Public file disclosure
    - SSL/TLS configuration suggestions
    - SPF/DMARC configuration suggestions
    - Phishing techniques

security_txt:
  served: false
  probed:
    - {url: 'https://moosend.com/.well-known/security.txt', status: 404}
    - {url: 'https://api.moosend.com/.well-known/security.txt', status: 404}
    - {url: 'https://docs.moosend.com/.well-known/security.txt', status: 404}
  note: >-
    The policy exists but is not machine-discoverable. An RFC 9116 security.txt
    naming Policy: https://moosend.com/privacy-policy/disclosure/ would close the
    gap with no new programme work.

evidence:
  - source: https://moosend.com/privacy-policy/disclosure/
    http_status: 200
    kind: disclosure-policy
    keywords: [vulnerability disclosure, bugcrowd, safe harbor, cfaa, dmca, submission form]
    fetched: '2026-08-13'
  - source: https://moosend.com/disclosure/
    http_status: 200
    kind: submission-form
    fetched: '2026-08-13'

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