Tripreporter
Approved changes feed: RSS · Atom
cpe:2.3:a:effectindex:tripreporter:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Effectindex (b0169320-c28e-5a59-af92-39f5c506d9b6) |
|---|---|
| Product | Tripreporter (6854c45a-fbc9-53aa-a95d-a6f1cd201fad) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2023-31123 |
vulnerable | 2026-06-08 06:04:41.883552 |
effectindex/tripreporter vulnerable to improper password verification on POST `/api/v1/account/login`
CRITICAL (9.1)
`effectindex/tripreporter` is a community-powered, universal platform for submitting and analyzing trip reports. Prior to commit bd80ba833b9023d39ca22e29874296c8729dd53b, any user with an account on an instance of `effectindex/tripreporter`, e.g. `subjective.report`, may be affected by an improper password verification vulnerability. The vulnerability allows any user with a password matching the password requirements to log in as any user. This allows access to accounts / data loss of the user. This issue is patched in commit bd80ba833b9023d39ca22e29874296c8729dd53b. No action necessary for users of `subjective.report`, and anyone running their own instance should update to this commit or newer as soon as possible. As a workaround, someone running their own instance may apply the patch manually.
Published: 2023-05-08T20:01:40.578Z
Updated: 2025-01-29T15:03:56.847Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.