different evaluation for the same vulnerability

### Current Behavior:
Dependency track is giving 2 different severity results for the same vulnérability.



the first one is on H2, the second is on PostgreSQL. i have noticed that working with postgresql is difficult, Dependency track does not fetch all the vulnerabilities; i have 140853 vulnerability in postgresql against 190232 in H2 (i have run it on docker so many times with postgresql and it never gets as much vulnerabilities as h2) now it is not giving the same evaluation

### Steps to Reproduce:
-run 2 containers on docker. one with h2, the other with PostgreSQL.
- add this component to your project on both containers and see the difference
purl: pkg:npm/handlebars@4.7.2

### Expected Behavior:

vulnerabilities' evaluation should be the same regardless of the DB used.

### Environment:

- Dependency-Track Version: 4.5.0 for both containers
- Distribution: [ Docker | Executable WAR | Traditional WAR ] docker
- BOM Format & Version: CycloneDX 1.3
- Database Server: [ H2 | MSSQL | MySQL | PostgreSQL ] one on H2, one on Postgresql
- Browser: edge

### Additional Details:
both evaluations are correct, but the h2 container is basing his on CVSSv3 which is the expected behavior, the one with postgresql is giving the CVSSv2 results.

(e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)