Comparison Overview

Givergy

VS

Benevolent Enabler

Givergy

The Studios, Rosedale Road, London, undefined, TW9 2SX, GB
Last Update: 2025-12-21
Between 750 and 799

Givergy is an award-winning technology company focussed on helping you achieve your fundraising goals through online fundraising solutions and at live events. We operate worldwide out of five regions in the UK, USA, Canada, Australia & Hong Kong. In the wake of Covid, we’ve redesigned our offering to cater for the new age of online fundraising and virtual events and, in the past eight months alone have helped over 700 charities raise more than $52 million USD for their amazing causes.

NAICS: 561499
NAICS Definition: All Other Business Support Services
Employees: 83
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Benevolent Enabler

1502 Music St., New Orleans, LA, US, 70117
Last Update: 2025-12-19
Between 750 and 799

Benevolent Enabler is a social impact technology to collect donations and data in the moment it matters. Our mobile platform offers non-profits a sustainable way to engage their donors in an innovative way. Benevolent Enabler's point of different is the 'digical experience' connecting the digital and physical worlds in useful merchandise and other tools. We are a social enterprise with a win:win mentality offering radical transparency to our non-profit community starting with a 1% fee model.

NAICS: 561499
NAICS Definition: All Other Business Support Services
Employees: 0
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/givergy.jpeg
Givergy
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
https://images.rankiteo.com/companyimages/benevolent-enabler.jpeg
Benevolent Enabler
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
Compliance Summary
Givergy
100%
Compliance Rate
0/4 Standards Verified
Benevolent Enabler
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Fundraising Industry Average (This Year)

No incidents recorded for Givergy in 2025.

Incidents vs Fundraising Industry Average (This Year)

No incidents recorded for Benevolent Enabler in 2025.

Incident History — Givergy (X = Date, Y = Severity)

Givergy cyber incidents detection timeline including parent company and subsidiaries

Incident History — Benevolent Enabler (X = Date, Y = Severity)

Benevolent Enabler cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/givergy.jpeg
Givergy
Incidents

No Incident

https://images.rankiteo.com/companyimages/benevolent-enabler.jpeg
Benevolent Enabler
Incidents

No Incident

FAQ

Benevolent Enabler company demonstrates a stronger AI Cybersecurity Score compared to Givergy company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Benevolent Enabler company has disclosed a higher number of cyber incidents compared to Givergy company.

In the current year, Benevolent Enabler company and Givergy company have not reported any cyber incidents.

Neither Benevolent Enabler company nor Givergy company has reported experiencing a ransomware attack publicly.

Neither Benevolent Enabler company nor Givergy company has reported experiencing a data breach publicly.

Neither Benevolent Enabler company nor Givergy company has reported experiencing targeted cyberattacks publicly.

Neither Givergy company nor Benevolent Enabler company has reported experiencing or disclosing vulnerabilities publicly.

Neither Givergy nor Benevolent Enabler holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Givergy company nor Benevolent Enabler company has publicly disclosed detailed information about the number of their subsidiaries.

Givergy company employs more people globally than Benevolent Enabler company, reflecting its scale as a Fundraising.

Neither Givergy nor Benevolent Enabler holds SOC 2 Type 1 certification.

Neither Givergy nor Benevolent Enabler holds SOC 2 Type 2 certification.

Neither Givergy nor Benevolent Enabler holds ISO 27001 certification.

Neither Givergy nor Benevolent Enabler holds PCI DSS certification.

Neither Givergy nor Benevolent Enabler holds HIPAA certification.

Neither Givergy nor Benevolent Enabler holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Versa SASE Client for Windows versions released between 7.8.7 and 7.9.4 contain a local privilege escalation vulnerability in the audit log export functionality. The client communicates user-controlled file paths to a privileged service, which performs file system operations without impersonating the requesting user. Due to improper privilege handling and a time-of-check time-of-use race condition combined with symbolic link and mount point manipulation, a local authenticated attacker can coerce the service into deleting arbitrary directories with SYSTEM privileges. This can be exploited to delete protected system folders such as C:\\Config.msi and subsequently achieve execution as NT AUTHORITY\\SYSTEM via MSI rollback techniques.

Risk Information
cvss4
Base: 8.5
Severity: LOW
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/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:X/R:X/V:X/RE:X/U:X
Description

The WP JobHunt plugin for WordPress, used by the JobCareer theme, is vulnerable to unauthorized modification of data due to a missing capability check on the 'cs_update_application_status_callback' function in all versions up to, and including, 7.7. This makes it possible for authenticated attackers, with Candidate-level access and above, to inject cross-site scripting into the 'status' parameter of applied jobs for any user.

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

The WP JobHunt plugin for WordPress, used by the JobCareer theme, is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 7.7 via the 'cs_update_application_status_callback' due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Candidate-level access and above, to send a site-generated email with injected HTML to any user.

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

The FiboSearch – Ajax Search for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's `thegem_te_search` shortcode in all versions up to, and including, 1.32.0 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This vulnerability requires TheGem theme (premium) to be installed with Header Builder mode enabled, and the FiboSearch "Replace search bars" option enabled for TheGem integration.

Risk Information
cvss3
Base: 5.4
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Description

The Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.11.0 via the ajax_get_members function. This is due to the use of a predictable low-entropy token (5 hex characters derived from md5 of post ID) to identify member directories and insufficient authorization checks on the unauthenticated AJAX endpoint. This makes it possible for unauthenticated attackers to extract sensitive data including usernames, display names, user roles (including administrator accounts), profile URLs, and user IDs by enumerating predictable directory_id values or brute-forcing the small 16^5 token space.

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