Quick answers
- Is CVE-2026-62033 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-62033 being exploited in the wild.
- How severe is CVE-2026-62033?
- High severity, with a CVSS score of 7.6, published 10 October 2026.
- Which products and versions are affected?
- uListing 2.2.0 and earlier.
- Is there a fix for CVE-2026-62033?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-62033 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-62033?
- Check whether you run uListing at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability permits unauthorized modification of subscriber settings in uListing through an unspecified mechanism. The attack vector and authentication requirements are not detailed in available sources, but the high CVSS score suggests network accessibility and significant impact on user data integrity or account control.
Affected products
- uListing 2.2.0 and earlier
Timeline
- 2026-10-10: disclosed