Comparison Overview

Oxford Playhouse

VS

Queensbury Theatre

Oxford Playhouse

Beaumont Street, Oxford, England, OX1 2, GB
Last Update: 2025-12-10
View Profile
Between 750 and 799
http://oxfordplayhouse.com

Positioned at the cultural heart of Oxfordshire, Oxford Playhouse inspires, engages and entertains a wide-reaching and diverse audience. It presents, produces and tours the highest quality middle-scale, small-scale and off-site theatre; supports and nurtures artists to make work; creates imaginative and ambitious participation opportunities for children and young people and provides exceptional cultural experiences for all.

NAICS: 711
NAICS Definition:
Employees: 62
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0
View Profile

Queensbury Theatre

None
Last Update: 2025-12-09
Between 750 and 799
http://queensburytheatre.org

After more than 55 years, The Country Playhouse is drawing back the curtain to present a new look and name — Queensbury Theatre. We are rolling out the red carpet to bring you the finest in classic and contemporary theatre with our new state-of-the-art 250-seat main stage and our innovative black box theater. Now is your chance to share in the excitement! Take a seat and get in on the ground floor to help grow our vision for Houston community theatre excellence. We’re giving the cue for a new beginning at Queensbury Theatre — where the stage awaits.

NAICS: 7111
NAICS Definition: Performing Arts Companies
Employees: 18
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/oxford-playhouse.jpeg
Oxford Playhouse
—
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/queensbury-theatre.jpeg
Queensbury Theatre
—
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
Oxford Playhouse
100%
Compliance Rate
0/4 Standards Verified
Queensbury Theatre
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Performing Arts Industry Average (This Year)

No incidents recorded for Oxford Playhouse in 2025.

Incidents vs Performing Arts Industry Average (This Year)

No incidents recorded for Queensbury Theatre in 2025.

Incident History — Oxford Playhouse (X = Date, Y = Severity)

Oxford Playhouse cyber incidents detection timeline including parent company and subsidiaries

Incident History — Queensbury Theatre (X = Date, Y = Severity)

Queensbury Theatre cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/oxford-playhouse.jpeg
Oxford Playhouse
Incidents

No Incident

https://images.rankiteo.com/companyimages/queensbury-theatre.jpeg
Queensbury Theatre
Incidents

No Incident

FAQ

Queensbury Theatre company demonstrates a stronger AI Cybersecurity Score compared to Oxford Playhouse company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Queensbury Theatre company has disclosed a higher number of cyber incidents compared to Oxford Playhouse company.

In the current year, Queensbury Theatre company and Oxford Playhouse company have not reported any cyber incidents.

Neither Queensbury Theatre company nor Oxford Playhouse company has reported experiencing a ransomware attack publicly.

Neither Queensbury Theatre company nor Oxford Playhouse company has reported experiencing a data breach publicly.

Neither Queensbury Theatre company nor Oxford Playhouse company has reported experiencing targeted cyberattacks publicly.

Neither Oxford Playhouse company nor Queensbury Theatre company has reported experiencing or disclosing vulnerabilities publicly.

Neither Oxford Playhouse nor Queensbury Theatre holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Oxford Playhouse company nor Queensbury Theatre company has publicly disclosed detailed information about the number of their subsidiaries.

Oxford Playhouse company employs more people globally than Queensbury Theatre company, reflecting its scale as a Performing Arts.

Neither Oxford Playhouse nor Queensbury Theatre holds SOC 2 Type 1 certification.

Neither Oxford Playhouse nor Queensbury Theatre holds SOC 2 Type 2 certification.

Neither Oxford Playhouse nor Queensbury Theatre holds ISO 27001 certification.

Neither Oxford Playhouse nor Queensbury Theatre holds PCI DSS certification.

Neither Oxford Playhouse nor Queensbury Theatre holds HIPAA certification.

Neither Oxford Playhouse nor Queensbury Theatre holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

NXLog Agent before 6.11 can load a file specified by the OPENSSL_CONF environment variable.

Published
Date
2025-12-14
Updated
Date
2025-12-14
Risk Information
cvss3
Base: 8.1
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
References
Description

uriparser through 0.9.9 allows unbounded recursion and stack consumption, as demonstrated by ParseMustBeSegmentNzNc with large input containing many commas.

Published
Date
2025-12-14
Updated
Date
2025-12-14
Risk Information
cvss3
Base: 2.9
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
References
Description

A vulnerability was detected in Mayan EDMS up to 4.10.1. The affected element is an unknown function of the file /authentication/. The manipulation results in cross site scripting. The attack may be performed from remote. The exploit is now public and may be used. Upgrading to version 4.10.2 is sufficient to fix this issue. You should upgrade the affected component. The vendor confirms that this is "[f]ixed in version 4.10.2". Furthermore, that "[b]ackports for older versions in process and will be out as soon as their respective CI pipelines complete."

Published
Date
2025-12-14
Updated
Date
2025-12-14
Risk Information
cvss2
Base: 5.0
Severity: LOW
AV:N/AC:L/Au:N/C:N/I:P/A:N
cvss3
Base: 4.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P/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
References
Description

MJML through 4.18.0 allows mj-include directory traversal to test file existence and (in the type="css" case) read files. NOTE: this issue exists because of an incomplete fix for CVE-2020-12827.

Published
Date
2025-12-14
Updated
Date
2025-12-14
Risk Information
cvss3
Base: 4.5
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:L
References
Description

A half-blind Server Side Request Forgery (SSRF) vulnerability exists in kube-controller-manager when using the in-tree Portworx StorageClass. This vulnerability allows authorized users to leak arbitrary information from unprotected endpoints in the control plane’s host network (including link-local or loopback services).

Published
Date
2025-12-14
Updated
Date
2025-12-14
Risk Information
cvss3
Base: 5.8
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N
References