CitiLights
noo-citilights · theme
Known security vulnerabilities for CitiLights. Find out in seconds which version runs on your site with WP Lens.
3 known vulnerabilities
2 exploitable without logging in · latest Mar 25, 2026
Before you install
Use with care
- 2 records needing no login published in the last two years.
- Not on wordpress.org (paid or third-party distribution); 3 known records.
If you install it, keep auto-updates on and monitor the site: when a new record appears you need to update quickly.
This assessment relies only on published vulnerability records and wordpress.org data; it does not review the code.
Is this component installed on your sites, and in which version? See it from inside the site with Noroxi Connector
Not in the wordpress.org directory (paid or third-party distribution). We cannot verify its latest release or maintenance status here; fixed-version data comes from the record itself.
wordpress.org status checked on Oct 17, 2026
Vulnerabilities
- High 8.8
CVE-2026-24974login required≤ 3.7.1
WordPress CitiLights theme <= 3.7.1 - PHP Object Injection vulnerability
- High 7.1
CVE-2026-24973unauthenticated · needs a click≤ 3.7.1
WordPress CitiLights theme <= 3.7.1 - Reflected Cross Site Scripting (XSS) vulnerability
- Medium 5.3
CVE-2026-25367unauthenticated≤ 3.7.2
WordPress CitiLights theme < 3.7.2 - Broken Access Control vulnerability
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).