---
title: "Security & Vulnerability Disclosure"
description: "This page outlines how JooThemes (joothemes.net), operated by Joomedia Sp. z o.o., manages security across our WordPress and Joomla! products, how researcher..."
url: "https://joothemes.net/security-vulnerability-disclosure"
category: Pages
date: "2026-06-15 10:17:28"
author: Jacek Nadolny
ai_policy: no_training
x-markdown-tokens: 1870
---

## Structured Data

- **Type:** Article
- **Title:** Security & Vulnerability Disclosure
- **URL:** https://joothemes.net/security-vulnerability-disclosure
- **Author:** Jacek Nadolny
- **Published:** 2026-06-15T10:17:28+02:00
- **Modified:** 2026-11-12T13:06:35+01:00


# Security & Vulnerability Disclosure

This page outlines how JooThemes (joothemes.net), operated by Joomedia Sp. z o.o., manages security across our WordPress and Joomla! products, how researchers and users can responsibly report potential vulnerabilities, and what response process you can expect from our team.
This security policy is published in English only. If you have any questions regarding its content, please reach out via our Contact page or email us directly at contact@joothemes.net.
1. Our Security Commitment
Our plugins, themes, extensions, and templates power production websites that real businesses and organizations rely on every day. Because a vulnerability in our code directly affects the security of our customers' websites, we treat every security report as a top priority rather than a routine support task.
Whenever a security flaw is confirmed, we investigate it promptly, develop a patch, and ship a security release as quickly as reasonably possible. Throughout the process, we keep the reporter updated and maintain transparency by publishing clear details of the issue and the fix once the update is available.
2. Supported Platforms & Lifecycle Policy
We can only guarantee security patches for CMS and PHP versions that are actively maintained by their respective upstream teams. Once WordPress, Joomla!, or PHP stops issuing security updates for a specific branch, we cannot mitigate underlying platform vulnerabilities within our software.
WordPress Support Policy
Because WordPress follows a continuous release cycle, we align our support with official WordPress core security maintenance:

| WordPress Branch | Upstream Maintenance Status | JooThemes Support Status |
| --- | --- | --- |
| Latest Major Release (6.x / 7.x) | Active bug fixes & security updates | Supported. Primary target platform. |
| Previous Major Release (N-1) | Security backports maintained by WordPress Core | Supported for critical security fixes. |
| Older Branches (6.0 & lower) | Security backports only (not recommended for production) | Not supported. Please update to the latest WordPress core. |

Joomla! Support Policy
For Joomla!, we follow an N / N-1 lifecycle policy: the current major release and the immediate preceding major release receive active security support. Security patches are always built and tested against the latest stable version within each supported branch.

| Version | End of Bug Fix Support | End of Security Support | JooThemes Support Status |
| --- | --- | --- | --- |
| Joomla! 6 | 17 Oct 2028 | 16 Oct 2029 | Supported. Primary target platform. |
| Joomla! 5 | 13 Oct 2026 | 12 Oct 2027 | Supported (security patches only) until Joomla! 5 reaches end of life. |
| Joomla! 4 | 15 Oct 2024 | 14 Oct 2025 | Not supported. End of life reached; please upgrade. |
| Joomla! 3 | 17 Aug 2021 | 17 Aug 2023 | Not supported. No security patches available. |

PHP Support Policy
We align our minimum and recommended server requirements with the official PHP release lifecycle:

| PHP Version | End of Active Support | End of Security Support | JooThemes Support Status |
| --- | --- | --- | --- |
| PHP 8.5 | 31 Dec 2027 | 31 Dec 2029 | Supported. |
| PHP 8.4 | 31 Dec 2026 | 31 Dec 2028 | Supported. Recommended for WordPress and Joomla! 6. |
| PHP 8.3 | 31 Dec 2025 | 31 Dec 2027 | Supported. |
| PHP 8.2 | 31 Dec 2024 | 31 Dec 2026 | Supported until upstream security support ends. |
| PHP 8.1 and lower | End of life | End of life | Not supported. |

If your website runs on an unsupported CMS or PHP release, we strongly urge you to plan an upgrade. Feel free to contact our team if you need guidance on verifying plugin or extension compatibility prior to upgrading.
3. Reporting a Security Vulnerability
If you discover a potential security vulnerability in any JooThemes plugin, theme, extension, or template, we encourage you to report it to us responsibly. Please refrain from disclosing the vulnerability publicly or sharing exploit details with third parties until we have had sufficient time to investigate, develop a fix, and distribute the patched release.
We follow a Coordinated Vulnerability Disclosure model. In return for responsible reporting, we commit to acknowledging your submission promptly, keeping you informed throughout remediation, and crediting your discovery in our release notes (should you wish to be acknowledged).
To help us reproduce and resolve the issue efficiently, please include the following details in your report:

- The exact name and version number of the affected JooThemes plugin, theme, extension, or template.

- The CMS platform (WordPress or Joomla!) and PHP version of the affected environment.

- A clear technical description of the vulnerability and its potential security impact.

- Step-by-step instructions required to reproduce the issue.

- Any relevant proof-of-concept (PoC) code, HTTP requests, or screenshots.

Please submit security reports via our Contact page or directly to contact@joothemes.net, clearly marking the subject line as "Security Vulnerability Report" so it is routed immediately to our engineering team.
4. Our Response & Remediation Process
Once a security report is received, we follow a structured workflow to ensure predictable communication:

- Acknowledgement (within 2 business days): We confirm receipt of your report and assign it an internal tracking reference.

- Initial Assessment (within 7 business days): Our developers attempt to reproduce the vulnerability, evaluate its severity (e.g., using CVSS criteria), and share our initial findings with you.

- Fix & Coordinated Release: We develop and test a security patch, coordinate the release timeline with you, and notify active subscribers via email on the day the update is published.

- Public Disclosure (within 30 days of release): Once users have had time to apply the patch, we publish an advisory in our release notes detailing the vulnerability, its severity, and the fix—including credit to the researcher if consent was provided.

Note: The timeframes above represent target benchmarks rather than contractual guarantees. As an agile engineering team, reports submitted during public holidays may occasionally require slightly longer to acknowledge, though critical vulnerabilities are always prioritized above standard development tasks.
5. EU Cyber Resilience Act (CRA) Compliance
The European Union Cyber Resilience Act (Regulation (EU) 2024/2847) establishes harmonized cybersecurity requirements for products with digital elements placed on the EU market. Under the regulation, mandatory reporting obligations for actively exploited vulnerabilities apply from 11 September 2026, with full manufacturer compliance obligations taking effect on 11 December 2027.
As an EU-based software developer, JOOMEDIA SP. Z O.O. is actively aligning our internal engineering workflows, vulnerability handling procedures, technical documentation, and software bill of materials (SBOM) processes to ensure full compliance with the Cyber Resilience Act across all our WordPress and Joomla! products.
We will update this page as our CRA compliance measures evolve. If you have specific compliance inquiries regarding any JooThemes product, please contact us at contact@joothemes.net.
---
## AI Usage Policy & Copyright Notice
**Status:** Machine-Readable TDM Opt-Out active (Directive EU 2019/790 Art. 4(3)).
This content is protected under the defined AI policy: No_training. Data mining and AI training restrictions apply.
