This page was not yet optimized for use on mobile devices.
CVE-2025-31500
Data
| Vulnerability ID | CVE-2025-31500 |
|---|---|
| Published on | 28.05.2025 18:15 |
| Severity | MEDIUM |
Vulnerable configurations
- cpe:2.3:a:bestpractical:request_tracker:5.0.0:*:*:*:*:*:*:*, cpe:2.3:a:bestpractical:request_tracker:5.0.1:*:*:*:*:*:*:*, cpe:2.3:a:bestpractical:request_tracker:5.0.2:*:*:*:*:*:*:*, cpe:2.3:a:bestpractical:request_tracker:5.0.3:*:*:*:*:*:*:*, cpe:2.3:a:bestpractical:request_tracker:5.0.4:*:*:*:*:*:*:*, cpe:2.3:a:bestpractical:request_tracker:5.0.5:*:*:*:*:*:*:*, cpe:2.3:a:bestpractical:request_tracker:5.0.6:*:*:*:*:*:*:*, cpe:2.3:a:bestpractical:request_tracker:5.0.7:*:*:*:*:*:*:*
Vulnerable certificates
This CVE has no assigned vulnerable CC or FIPS certificates.
Looking for more?
Explore the landscape of Common Criteria and FIPS 140 certificates.