Ville de Saint-Pair-sur-Mer
- Known vulnerabilities
- 0
- Still open
- 0
- KEV open
- 0
- Max CVSS (historical)
- —
Cumulative exposure
Low
Aggregates open CVEs (40%) + KEV (30%) + critical shared permissions (15%) + trackers (10%) + OS EOL (5%). Higher score = more exposed.
-
Open CVEs +0/+50
0 open CVEs, max CVSS 0.0, EPSS 0%
-
Active KEVs +0/+35
0 CISA KEVs still open
-
Permissions +0/+10
0 critical shared permission(s)
-
Trackers +0/+8
0 identification/profiling tracker(s)
-
EOL OS +0/+5
Installed OS is end-of-life
Based on permissions only: no CVE data referenced for this app.
Known vulnerabilities (CVE)
No CVE is currently referenced in NVD for this app on its platform.
The absence of CVEs is not a security guarantee — it can also mean nobody has audited or published findings.
Context
Context
Description
Town of St-Pair-sur-Mer: simplify your procedures and follow the news daily
Data collected and shared
Source: Play Store Data Safety · 14 data item(s) declared
Indicative classification based on data sensitivity. "Shared" = transmitted to third parties (publisher-declared).
FAQ
FAQ: Ville de Saint-Pair-sur-Mer
Why are no CVEs listed for Ville de Saint-Pair-sur-Mer?
No CVE is currently referenced in NVD for Ville de Saint-Pair-sur-Mer (com.arpege.mcity.saintpairsurmer) with a Android CPE configuration. Either none has been publicly disclosed, or none has been mapped yet. Absence of a CVE is not a security guarantee.
What is the latest known version of Ville de Saint-Pair-sur-Mer?
The most recent version of Ville de Saint-Pair-sur-Mer (com.arpege.mcity.saintpairsurmer) tracked by Appaloosa Scout is 3.04.030, published by Ville de Saint Pair sur Mer.