Skip to content

MoEngage

Vulnerability disclosure program on security.txt moengage.com

Accepting reports Full safe harbor security.txt
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
3
Public CVEs
0
Last change
No changes yet

At a glance

What to know before you start testing.

No cash rewards
A disclosure program: you report for credit, not money.
Report by email
[email protected]
Full safe harbor
Good-faith research is authorised; no legal action.
Replies within 1 day
As the policy promises.
No public write-ups
Keep findings private.

Rewards

What the company's own policy page says it pays.

This program does not pay cash rewards.

Pays cash
No MoEngage does not currently offer a monetary bug bounty program.
Response
Within 1 days Initial Response: We will acknowledge your report within 24 hours .
Safe harbor
Full MoEngage considers research conducted under this policy to be authorized and protected.
Hall of fame
Yes If you submit a valid and unique vulnerability report, we will be pleased to add you to our Security Hall of Fame (with your permission).

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

3 assets you may test, 2 excluded.

Domains 1

  • moengage.com

Wildcard domains 1

  • *.moengage.com

Products and areas 1

  • MoEngage Mobile SDKs (iOS & Android)
Out of scope (2)
  • MoEngage Corporate IT: Internal employee systems, office networks, and VPN endpoints
  • Third-Party Services: Services or vendors used by MoEngage (e.g., cloud providers, helpdesk software, marketing tools)

Rules

What the policy asks of you, and the bug types it won't reward, quoted from MoEngage's policy.

While testing

  • Do not test on accounts you do not own.
  • Testing that affects real customer data, corrupts production databases, or degrades service quality is strictly prohibited.
  • Stop immediately if you encounter non-public data (PII, financial info, proprietary code). Do not view, save, or transfer it.
  • Purge any local copies of incidental data you may have downloaded.
  • Use custom scripts or low-intensity scanning tools only.
  • Exfiltrate Data: Do not download data to prove a vulnerability. Showing you can access one record is sufficient proof; accessing ten is excessive.
  • Disrupt Services: Do not use high-volume automated scanners (e.g., Nessus, Burp Intruder) without rate limiting, as this may trigger DoS protections.
  • Social Engineering: Phishing employees or customers is strictly prohibited.
  • Physical Attacks: Do not attempt to access MoEngage offices.

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 3 hours ago.

No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.

Public CVEs

Published vulnerabilities in this vendor's products, from the NVD.

Search NVD

No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.