unassigned severity while the score is set for the vulnerability

### Current Behavior



Hey guys,
I am using Dependecy track for a project and I just noticed that some vulnerabilities have the unassigned status while when you search the vulnerability on the NVD you see the actual score of the vulnerability.
Also, the link that Dependecy track gives you on the vulnerability clearly says the severity of the vulnerability so I do not understand why the status is unassigned .

### Steps to Reproduce

1.upload a BOM with windows 10 family edition (version: 10.0.19045.3930)
2. Watch the latest vulnerabilities
The BOM I use only has windows family edition and here are some screenshots has an example of the issue.

### Expected Behavior

I would expect to have the severity of the CVE instead of (UNASSIGNED ) as is it shown in NVD database.

### Dependency-Track Version

4.12.6

### Dependency-Track Distribution

Executable WAR

### Database Server

H2

### Database Server Version

_No response_

### Browser

Mozilla Firefox

### Checklist

- [x] I have read and understand the [contributing guidelines](https://github.com/DependencyTrack/dependency-track/blob/master/CONTRIBUTING.md#filing-issues)
- [x] I have checked the [existing issues](https://github.com/DependencyTrack/dependency-track/issues) for whether this defect was already reported