MyReviews
|4,40Last 180 days
MyReviews is a popular Russian service for automating the collection, monitoring, and management of customer reviews. It helps businesses track their online reputation, gather feedback, and improve their search engine rankings.
Rewards are paid to individual entrepreneurs and self-employed persons
Program description
MyReviews Bug Bounty Program Rules
Important scope restriction. This program accepts findings with a demonstrated security impact: unauthorized access to non-public data, modification or deletion of another user's data, account takeover, disclosure of valid authentication credentials not intended for you, or impact on MyReviews infrastructure. Do not submit reports solely about bypassing payment, obtaining paid features, demo or trial access, or bypassing plan and quota restrictions, including parsing and auto-reply quotas. Such outcomes alone are out of scope, even if the feature actually worked. See Sections 3 and 6 for details.
Common out-of-scope examples: restarting or extending a demo; connecting a paid review source and collecting reviews on the Free plan; generating or publishing an auto-reply for your own account without the required plan; exporting your own reviews through the API; creating additional firms, groups, widgets, or quotas in your own account. Do not test these solely for a report unless you can separately demonstrate a security violation affecting another account or non-public data.
1. Accepted languages
- Russian;
- English.
2. Scope
Only the following assets are in scope:
myreviews.ru;myreviews.dev;- subdomains of
*.myreviews.dev.
If an asset is not on this list, it is out of scope. Mentioning a domain in code, CSP, DNS, historical records, or a third-party integration does not bring it into scope.
Current REST API documentation is available at:
https://myreviews.ru/api-docs
The documentation can help you understand an endpoint's purpose, request format, and authorization requirements. However, whether a method appears in the documentation does not, by itself, establish a vulnerability. We need a demonstrated exploitation outcome.
3. Findings we are interested in
Submit a report if you have safely demonstrated at least one of the following outcomes on an asset listed in Section 2:
- unauthorized reading of another user’s or organization’s non-public data;
- unauthorized modification or deletion of another user’s or organization’s data, including performing an action on their behalf;
- takeover of another user’s account or the ability to perform protected actions with the account owner’s privileges;
- obtaining valid authentication credentials not intended for you that allow access to another account or a protected resource;
- code execution, control over MyReviews infrastructure, or other demonstrated access to protected internal resources with a significant security impact.
Show what you can access or do without the required privileges and the actual protected outcome. For testing, use your own test accounts and objects with different permission levels; do not access other people’s data without prior authorization. A demonstrated security impact can arise in any feature, but using a paid feature or exceeding a limit does not, by itself, constitute such an impact. Exclusions are listed in Section 6.
4. High-impact findings
In particular, we consider a finding potentially high-impact when you safely demonstrate:
- takeover of another user’s account or actions performed on behalf of its owner;
- obtaining valid authentication credentials not intended for the researcher;
- access to a substantial volume of non-public sensitive user data;
- large-scale unauthorized reading, modification, or deletion of other accounts’ data;
- code execution or control over MyReviews infrastructure.
These reports are assessed individually. A vulnerability class, CVE identifier, or high CVSS score does not automatically make a report Critical. The report must show an actual outcome. Acceptance is not limited to Critical severity: demonstrated cross-account reading, modification, or deletion of non-public data, acquisition of valid authentication credentials, and account takeover are considered at any justified severity, including when only one account is affected. Large-scale impact is not required for acceptance.
5. How to demonstrate a vulnerability
We need reproducible steps and an actual protected outcome from Section 3. For cross-account testing, use two accounts you own or accounts whose owners have expressly authorized the test; show the permissions held by each account.
The following do not, on their own, constitute proof:
- an assumption that the vulnerability could be developed into a more serious attack;
- a change visible only in the interface without a demonstrated server-side effect;
- an unusual API response without an outcome available to the attacker;
- a misconfigured security control without a working exploit;
- a theoretical attack chain without a completed proof of concept;
- a change to a plan status, counter, job, or technical record without a protected outcome from Section 3.
Use the minimum number of requests and objects necessary for testing. Stop as soon as the outcome has been demonstrated.
What we consider authentication credentials
- a password or its equivalent;
- a password hash;
- a valid session, access, or refresh token;
- an API key;
- an account-recovery token or code.
An email address, UUID, numeric ID, internal name, status, or other technical metadata is not an authentication credential unless it can, by itself, be used to sign in, access non-public data, or act on behalf of a user.
6. What we do not accept
If the demonstrated outcome does not fall under Section 3, the report will be closed as Out of Scope. The vulnerability class or CVSS score does not change this.
Explicit exclusion: bypassing payment; activating or extending a paid plan without payment; obtaining a paid feature, resource, quota, or limit; demo or trial access and its extension or bypass; and bypassing plan, parsing, or auto-reply restrictions—including obtaining parsing results beyond a quota or sending auto-replies beyond a limit—are not accepted on their own, even when the feature was actually used. This also applies to paid capabilities exposed by an API when the corresponding button is unavailable in the interface. If, while investigating such a feature, you independently demonstrate unauthorized reading, modification, or deletion of another user’s non-public data, account takeover, acquisition of valid authentication credentials not intended for you, or protected impact on infrastructure, describe that security outcome from Section 3 rather than the plan bypass.
The following, on their own, are also not accepted:
- software versions, headers, stack traces, internal hostnames, IP addresses, paths, and diagnostic messages;
- CORS, CSP, CSRF, SameSite, X-Frame-Options, Secure, HttpOnly, and other settings without a working exploit;
- open redirects, HTTP
OPTIONS/TRACE, missing security headers, and other hardening observations; - a report based solely on a software version or CVE;
- theoretical scenarios and issues in unreachable legacy code;
- missing CAPTCHA, SMS verification, or rate limiting;
- a weak password policy and user enumeration;
- a long token lifetime without a way to obtain and use another user’s token;
- logout CSRF and observations about stateless JWTs without access to another account;
- registration with an unverified email address and login to an account you created yourself;
- brute force and credential stuffing;
- spam and abuse of public forms;
- DoS/DDoS, holding connections open, and resource exhaustion;
- self-XSS and XSS that works only in your own account;
- blind SSRF, an external out-of-band callback, or internal network reachability without a demonstrated protected outcome;
- attacks that require control of the victim’s device, browser, or local network;
- DNS, DMARC, SPF, DKIM, and DNSSEC observations;
- IDN homograph attacks, Broken Link Hijacking, and Domain Hijacking without an outcome from Section 3;
- issues in a third-party service without a direct impact on MyReviews.
XSS, CSRF, SSRF, IDOR, injection, race conditions, and other recognized vulnerability classes are not automatically in scope. XSS and SSRF are considered only when a protected outcome from Section 3 has been safely demonstrated; a payload, alert, callback, or reachability alone is insufficient.
7. MyReviews-specific behavior
This section explains product behavior; it does not expand the program’s scope.
Public firm and widget data
MyReviews serves public data for firm profiles and widgets on customers’ websites. Accessing that data without authentication, with another user’s JWT, or by a sequential ID is not, by itself, an IDOR.
This includes, in particular, the following APIs:
GET /v1/firm/view?id=<id>;GET /v1/widget/get-firm/...;GET /v1/widget/get-reviews/...;- other methods that return public profile or widget data.
In this context, public or technical data includes:
- a firm’s name, address, image, website, and description;
- UUID, numeric ID,
parent_id, and object type; - ratings, counts, and the text of public reviews, links, avatars, and photographs;
- connected review sources, dates, statuses, and aggregate counters;
- public widget, QR-code, or profile configuration;
- setting flags, provided they do not disclose recipients, tokens, authentication credentials, or notification contents;
isPaid,active, and other status values that do not, by themselves, grant access to non-public data or another user’s privileges.
A
false response from GET /v1/firm/access means the requester lacks permission to perform account operations; it does not make the public profile confidential.Do not enumerate identifiers at scale. Your own test objects are sufficient for a proof of concept.
Reviews and widgets
Review text, links, avatars, photographs, and metadata from public review platforms are not considered confidential.
A public review-creation endpoint or feedback form is not a vulnerability on its own.
Test review creation only on your own test firms. Do not publish even a single test review, payload, or text such as
test XSS or test CSRF on a real customer’s profile without prior authorization: the review becomes public and visible to users.The number of widgets for one firm is not limited. Creating multiple widgets is an intended feature of the service.
Records, statuses, and counters
A newly created firm or job record, a changed counter or status, or a
200 OK response does not, by itself, demonstrate unauthorized access to non-public data or another user’s privileges. A demonstrated outcome from Section 3 is required. Plan and quota bypasses are excluded by Section 6.Parsers and auto-replies
A server request to an allowed external review platform is part of normal parsing. Using a parser or auto-replies beyond plan limits is out of scope on its own. Unauthorized sending of a reply on behalf of another account or organization with a demonstrated effect may fall under Section 3; test this only with your own test objects and without publishing anything on real customers’ profiles.
SSRF
Blind SSRF, an external out-of-band callback, and the ability to reach an internal network are not accepted on their own. SSRF is considered when a protected outcome from Section 3 has been safely demonstrated, such as access to sensitive internal data or valid credentials, or control over infrastructure. Merely reaching an internal address, metadata service, or trusted endpoint is insufficient without such an outcome.
For safe internal reachability testing, use only:
192.168.4.72:8000
Do not scan internal address ranges, metadata endpoints, ports, or services without written authorization.
8. Safe testing
Use only:
- your own accounts;
- accounts belonging to users who have expressly authorized the test;
- test accounts provided by MyReviews.
Usually, two accounts you own and a few of your own objects are sufficient for a proof of concept. If this is insufficient, arrange the test with us first.
Please stop testing as soon as the outcome has been demonstrated.
Without prior authorization, you may not:
- access other people’s accounts, data, or resources;
- enumerate IDs, email addresses, logins, firms, or other objects at scale;
- send requests, messages, emails, reviews, or files in bulk;
- publish test reviews, payloads, or references to vulnerabilities on other firms’ profiles;
- conduct load testing or take actions that may cause a DoS/DDoS;
- use social engineering or phishing;
- attack employees, customers, or partners;
- upload malware, spyware, large files, or dangerous files;
- modify, delete, or replace server files other than files in your own test accounts.
If you discover a way to read arbitrary files on a server, you may read only:
/etc/ufw/user6.rules
Obtain written authorization before taking any other action involving files.
9. What to include in your report
Include:
- what happened and why it is a vulnerability;
- which protected outcome from Section 3 you demonstrated;
- the affected asset and endpoint;
- minimal reproduction steps;
- requests and responses with secrets redacted;
- IDs of test accounts and objects, and the distinction between their permissions;
- the date and time of testing;
- screenshots, videos, or other supporting materials;
- recommendations for remediation.
Do not publish active tokens, passwords, keys, or personal data. Redact them from text, screenshots, and videos.
If demonstrating the impact would require accessing another person’s data, affecting infrastructure, or disrupting the service, contact the program team first.
10. Severity and rewards
We first check whether the demonstrated outcome from Section 3 is in scope and whether the safe-testing rules were followed. We then determine severity and the reward amount.
We consider:
- the demonstrated protected outcome;
- the affected non-public data and privileges;
- the prerequisites and complexity of exploitation;
- whether the victim must take any action;
- the number of affected users and resources;
- impact on accounts and infrastructure.
The program’s maximum reward is 50,000 RUB before tax.
0-day and 1-day vulnerabilities are assessed individually if they meet the criteria in Section 3.
11. Duplicates
The reward is awarded to the first report that contains sufficient information to reproduce and fix a previously unknown vulnerability.
A report is considered a duplicate if, before it was received, we already had a report, internal audit finding, or task containing sufficient information about the same root cause.
A different endpoint, a new exploitation technique, or a more detailed proof of concept is not a separate vulnerability if fixing it requires addressing the same root cause.
Duplicates are not rewarded.
12. How to Request Additional Testing Time
- Register your own test accounts.
- Send the registration email address and a link to your verified Standoff 365 profile to
bugbounty@myreviews.ru. - After reviewing the information, the program team may add extra paid-plan testing time to your account.