Skip to content

AhaSlides Pte Ltd

Vulnerability disclosure program on security.txt ahaslides.com

Accepting reports Full safe harbor security.txt
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
5
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 2 days
As the policy promises.
Publish after a fix
Coordinate the timing with the company.

Rewards

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

This program does not pay cash rewards.

Response
Within 2 days Acknowledgement within 2 business days .
Safe harbor
Full We will not take legal action against you for security research conducted in good faith under this policy.
Hall of fame
Yes Public credit in our security acknowledgements, if you would like it.

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

Scope

5 assets you may test, 6 excluded.

Domains 3

  • ahaslides.com
  • audience.ahaslides.com
  • presenter.ahaslides.com

Wildcard domains 1

  • ahaslides.com and its subdomains

Products and areas 1

  • The AhaSlides web application, presenter and audience apps
Out of scope (6)
  • Denial-of-service (DoS/DDoS) and volumetric or traffic-flooding tests
  • Open (unauthenticated) audience access
  • Reports affecting only unsupported or end-of-life browsers
  • Social engineering of staff, users or contractors; physical attacks
  • Spam, or findings from automated scanners without a demonstrated, exploitable impact
  • Third-party services we do not control (raise those with the third party)

Rules

What the policy asks of you, and the bug types it won't reward, quoted from AhaSlides Pte Ltd's policy. "We" in these lines means the program, not this site.

While testing

  • Report as soon as you find an issue, and give us reasonable time to fix it before disclosing publicly.
  • Use only your own test accounts. Stop at proof-of-concept.
  • Access, modify, download, or delete data that is not your own.
  • To prove access, a screenshot or a minimal, redacted record is enough, so do not exfiltrate real user data.
  • Degrade or interrupt our services, or run automated high-volume attacks.
  • Publicly disclose the issue before we have confirmed it is resolved (see Coordinated disclosure ).

Not accepted

  • Denial-of-service (DoS/DDoS) and volumetric or traffic-flooding tests
  • Social engineering of staff, users or contractors; physical attacks
  • Spam, or findings from automated scanners without a demonstrated, exploitable impact
  • Reports affecting only unsupported or end-of-life browsers
  • Reports that the audience join or submission flow lacks authentication are not treated as vulnerabilities.
  • Best-practice suggestions with no security impact (for example missing headers with no exploit, SPF/DMARC nitpicks, self-XSS, rate-limiting opinions).

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 12 Nov 2026. Last checked 2 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.