Comparison Overview

CURA COSMETICS GROUP

VS

VIE at home

CURA COSMETICS GROUP

Dr.-Franz-Werner-Straโˆšรผe 19 Innsbruck, Tirol 6020, AT
Last Update: 2025-03-17 (UTC)

Excellent

Cura Marketing ist ein Dienstleistungsunternehmen im Bereich der Kosmetik und beschโˆšยงftigt sich mit der Entwicklung von Marken, Marketingkonzepten und Vermarktungsstrategien fโˆšยบr Kosmetik. Cura Marketing, mit Firmensitz in Innsbruck, beschโˆšยงftigt 95 Mitarbeiter, agiert europaweit in 8 Lโˆšยงndern, setzt jโˆšยงhrlich 45 Mio. โ€šร‡ยจ um und weist eine Exportquote von โˆšยบber 95% auf. Erfahren Sie mehr unter: www.curacosmetic.com

NAICS: None
NAICS Definition: Others
Employees: 201-500
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

VIE at home

City Fields, Tangmere Chichester, West Sussex PO19 3BX, GB
Last Update: 2025-03-15 (UTC)

Excellent

Between 900 and 1000

Award winning Skin Care, Make Up and Bath & Body products. Shop with VIE at home online or hold a Party with one of our UK wide Consultants. And we don't just sell Make Up! You can also buy trend inspired Jewellery, gorgeous Homeware and fantastic Aromatherapy products to help treat your mood. Our philosophy remains the same as it was when we originally launched in 1997 (under our previous name Virgin Vie At Home): premium products at affordable prices that can be enjoyed from the comfort of your own home.

NAICS: None
NAICS Definition:
Employees: 10,001+
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/cura-marketing-gmbh.jpeg
CURA COSMETICS GROUP
โ€”
ISO 27001
Not verified
โ€”
SOC 2
Not verified
โ€”
GDPR
No public badge
โ€”
PCI DSS
No public badge
https://images.rankiteo.com/companyimages/vie-at-home.jpeg
VIE at home
โ€”
ISO 27001
Not verified
โ€”
SOC 2
Not verified
โ€”
GDPR
No public badge
โ€”
PCI DSS
No public badge
Compliance Summary
CURA COSMETICS GROUP
100%
Compliance Rate
0/4 Standards Verified
VIE at home
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Cosmetics Industry Average (This Year)

No incidents recorded for CURA COSMETICS GROUP in 2025.

Incidents vs Cosmetics Industry Average (This Year)

No incidents recorded for VIE at home in 2025.

Incident History โ€” CURA COSMETICS GROUP (X = Date, Y = Severity)

CURA COSMETICS GROUP cyber incidents detection timeline including parent company and subsidiaries

Incident History โ€” VIE at home (X = Date, Y = Severity)

VIE at home cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/cura-marketing-gmbh.jpeg
CURA COSMETICS GROUP
Incidents

No Incident

https://images.rankiteo.com/companyimages/vie-at-home.jpeg
VIE at home
Incidents

No Incident

FAQ

Both CURA COSMETICS GROUP company and VIE at home company demonstrate a comparable AI risk posture, with strong governance and monitoring frameworks in place.

Historically, VIE at home company has disclosed a higher number of cyber incidents compared to CURA COSMETICS GROUP company.

In the current year, VIE at home company and CURA COSMETICS GROUP company have not reported any cyber incidents.

Neither VIE at home company nor CURA COSMETICS GROUP company has reported experiencing a ransomware attack publicly.

Neither VIE at home company nor CURA COSMETICS GROUP company has reported experiencing a data breach publicly.

Neither VIE at home company nor CURA COSMETICS GROUP company has reported experiencing targeted cyberattacks publicly.

Neither CURA COSMETICS GROUP company nor VIE at home company has reported experiencing or disclosing vulnerabilities publicly.

Neither CURA COSMETICS GROUP company nor VIE at home company has publicly disclosed detailed information about the number of their subsidiaries.

Neither CURA COSMETICS GROUP company nor VIE at home company has publicly disclosed the exact number of their employees.

Latest Global CVEs (Not Company-Specific)

Description

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in The Wikimedia Foundation MediaWiki Cargo extension allows SQL Injection.This issue affects MediaWiki Cargo extension: 1.39, 1.43, 1.44.

Risk Information
cvss4
Base: 2.1
Severity: HIGH
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:N/AU:Y/R:U/V:C/RE:M/U:Amber
Description

Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in The Wikimedia Foundation MediaWiki QuizGame extension allows Stored XSS.This issue affects MediaWiki QuizGame extension: 1.39, 1.43, 1.44.

Risk Information
cvss4
Base: 2.0
Severity: HIGH
CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:N/AU:N/R:U/V:C/RE:M/U:Amber
Description

Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in The Wikimedia Foundation MediaWiki PollNY extension allows Stored XSS.This issue affects MediaWiki PollNY extension: 1.39, 1.43, 1.44.

Risk Information
cvss4
Base: 2.0
Severity: HIGH
CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:N/AU:N/R:U/V:C/RE:M/U:Amber
Description

Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in The Wikimedia Foundation MediaWiki WebAuthn extension allows Stored XSS.This issue affects MediaWiki WebAuthn extension: 1.39, 1.43, 1.44.

Risk Information
cvss4
Base: 5.8
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:A/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:N/R:U/V:C/RE:L/U:Amber
Description

pyquokka is a framework for making data lakes work for time series. In versions 0.3.1 and prior, the FlightServer class directly uses pickle.loads() to deserialize action bodies received from Flight clients without any sanitization or validation in the do_action() method. The vulnerable code is located in pyquokka/flight.py at line 283 where arbitrary data from Flight clients is directly passed to pickle.loads(). When FlightServer is configured to listen on 0.0.0.0, this allows attackers across the entire network to perform arbitrary remote code execution by sending malicious pickled payloads through the set_configs action. Additional vulnerability points exist in the cache_garbage_collect, do_put, and do_get functions where pickle.loads is used to deserialize untrusted remote data.

Risk Information
cvss3
Base: 9.8
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H