Skip to content
bugbounty.fyi
Get paid to secure open source 475 paid open-source programs on Sorona, up to $1M Perk Low bugs: $100 or 1 mo Claude Max

Also on Patchstack. All 476 paid open-source programs

Try

Highest paying Newly launched Paid without KYC Full safe harbor
All results

About this site

London Metropolitan University

Vulnerability disclosure program on security.txt londonmet.ac.uk

Accepting reports security.txt
Go to program Website
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
2
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]
Partial safe harbor
Some legal protection; read the terms.
Replies within 10 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.

Pays cash
No we do not offer monetary rewards for vulnerability disclosures.
Response
Within 10 days we will respond to your report within 10 working days
Safe harbor
Partial This policy is designed to be compatible with common vulnerability disclosure good practice. It does not give you permission to act in any manner that is inconsistent with the law
Hall of fame
Yes London Metropolitan like to thank the researchers who identified and reported findings to us, you can brows the list by reading credits.tx t file

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

Scope

2 assets you may test, 1 excluded.

Domains 2

  • lmu.ac.uk
  • londonmet.ac.uk
Out of scope (1)
  • All systems not explicitly mentioned as in-scope.

Rules

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

While testing

  • Break any applicable law or regulations.
  • Access unnecessary, excessive or significant amounts of data.
  • Modify data in the Organisation's systems or services.
  • Exfiltrate Data. Use a proof of concept to demonstrate the vulnerability
  • Use high-intensity invasive or destructive scanning tools to find vulnerabilities.
  • Attempt or report any form of denial of service, e.g. overwhelming a service with a high volume of requests.
  • Disrupt the Organisation's services or systems.
  • Communicate any vulnerabilities or associated details other than by means described in the published security.txt.
  • Social engineer, 'phish' or physically attack the Organisation's staff or infrastructure.
  • Demand financial compensation in order to disclose any vulnerabilities.

Not accepted

  • non-exploitable vulnerabilities
  • reports indicating that the services do not fully align with 'best practice', for example missing security headers
  • TLS configuration weaknesses, for example 'weak' cipher suite support or the presence of TLS1.0 support

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