Mixing "CVE" format pattern case for Python packages

Describe the bug

I noticed that in [1] and [2] there are a mix of CVE format pattern. Basically, there are lower and upper case.

Is there any specific reason why cve-2024-7592 is lowercase in both advisories?

Affecting Photon 5 and 4.

Refs
[1] https://github.com/vmware/photon/wiki/Security-Update-5.0-386
[2] https://github.com/vmware/photon/wiki/Security-Update-4.0-704

Reproduction steps

1. Download feed 5 or 4
2. run

cve_data_photon5.0.json | jq '.[] | select (.cve_id == "cve-2024-7592")'
{
  "cve_id": "cve-2024-7592",
  "pkg": "python3",
  "cve_score": 7.5,
  "aff_ver": "all versions before 3.11.9-4.ph5 are vulnerable",
  "res_ver": "3.11.9-4.ph5"
}
{
  "cve_id": "cve-2024-7592",
  "pkg": "python3-libs",
  "cve_score": 7.5,
  "aff_ver": "all versions before 3.11.9-4.ph5 are vulnerable",
  "res_ver": "3.11.9-4.ph5"
}
{
  "cve_id": "cve-2024-7592",
  "pkg": "python3-xml",
  "cve_score": 7.5,
  "aff_ver": "all versions before 3.11.9-4.ph5 are vulnerable",
  "res_ver": "3.11.9-4.ph5"
}
{
  "cve_id": "cve-2024-7592",
  "pkg": "python3-curses",
  "cve_score": 7.5,
  "aff_ver": "all versions before 3.11.9-4.ph5 are vulnerable",
  "res_ver": "3.11.9-4.ph5"
}
{
  "cve_id": "cve-2024-7592",
  "pkg": "python3-devel",
  "cve_score": 7.5,
  "aff_ver": "all versions before 3.11.9-4.ph5 are vulnerable",
  "res_ver": "3.11.9-4.ph5"
}
{
  "cve_id": "cve-2024-7592",
  "pkg": "python3-tools",
  "cve_score": 7.5,
  "aff_ver": "all versions before 3.11.9-4.ph5 are vulnerable",
  "res_ver": "3.11.9-4.ph5"
}
{
  "cve_id": "cve-2024-7592",
  "pkg": "python3-test",
  "cve_score": 7.5,
  "aff_ver": "all versions before 3.11.9-4.ph5 are vulnerable",
  "res_ver": "3.11.9-4.ph5"
}
{
  "cve_id": "cve-2024-7592",
  "pkg": "python3-macros",
  "cve_score": 7.5,
  "aff_ver": "all versions before 3.11.9-4.ph5 are vulnerable",
  "res_ver": "3.11.9-4.ph5"
}

Expected behavior

a standard format pattern for CVE string

Additional context

No response

Start with the cve_data_photon5.0.json feed and the reported jq query, then compare the corresponding Photon 4 output and the linked security-update references. Trace where cve_id values are produced and establish a consistent CVE casing; done means both feeds use the same standard format for this advisory and similar entries.