Comparison Overview
City of Inman

City of Inman
20 S Main St, Inman, 29349, US
Last Update: 26/03/2026
City of Inman | The Official Website of the City of Inman, South Carolina. Visit cityofinman.org for City Government, Administration, Major and City Council, Municipal Court, Business Resources, Planning and Zoning, Public Resources and Services, Wastewater Treatment, R...

Comunidad de Madrid
Plaza de la Puerta del Sol, 7, Madrid, 28013, ES
Last Update: 31/03/2026
Si necesitas información general y especializada sobre los servicios públicos madrileños puedes llamar al teléfono de Atención al Ciudadano 012. En la Comunidad de Madrid estamos encantados de recibir comentarios y favorecer el diálogo, por eso te proponemos unas nor...
Compliance Ranges Comparison

City of Inman







Comunidad de Madrid






Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
City of Inman has 31.97% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Comunidad de Madrid in 2026.
Incident History - City of Inman (X = Date, Y = Severity)
City of Inman cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Comunidad de Madrid (X = Date, Y = Severity)
Comunidad de Madrid cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

City of Inman

Comunidad de Madrid
FAQ
Latest Global CVEs
A vulnerability has been found in SourceCodester Simple Online Food Ordering System 1.0. This affects an unknown function of the file /admin/ajax.php?action=login2. The manipulation of the argument email leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.
A flaw was found in the ipa_getkeytab module of the community.general Ansible collection. The module's bind_pw parameter, used to supply the LDAP simple-bind password when retrieving a Kerberos keytab, is not declared with no_log, unlike the sibling password parameter in the same module. As a consequence, the supplied IPA/LDAP bind password is recorded in cleartext in the managed host's system journal/syslog (the module's "Invoked with" record), is included in the module's return values and verbose (-v) output, and is displayed in Automation Controller / AWX job output. The password is additionally passed on the command line to the ipa-getkeytab helper (as --bindpw <value>), exposing it in the process list to local users while the command runs. An attacker able to read these logs, job output, or the process table can obtain the directory bind credential, potentially compromising the accounts and objects that credential can access.
The device metadata import interface /device/instance/{productId}/property-metadata/import of jetlinks community 2.11 is vulnerable to Server-side request forgery (SSRF).
disconf (Distributed Configuration Management Platform) 2.6.36 is vulnerable to Incorrect Access Control. The config-fetching APIs /api/config/item, /api/config/file, /api/config/list and /api/config/simple/list are exposed without authentication. The LoginInterceptor explicitly whitelists these four paths, so any anonymous attacker can read every configuration item and configuration file managed by the config center.
Funiture 1.0.0 is vulnerable to SQL Injection in the backend tool interfaces /sys/tool/select.json and /sys/tool/update.json.