HomeWordPress vulnerabilitiesQyrr
Qyrr vulnerabilities
Qyrr has 2 known vulnerabilities in this database. The most recent published record is dated 30 Sep 2025.
- Known vulnerabilities
- 2
- Active installs
- 2,000+
- Latest version
- 2.0.13
- Last updated
- 14 Aug 2026
- Most recent
- 30 Sep 2025
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Remote code execution CVE-2025-10000 | Medium 6.4 | Up to 2.0.7 | Fixed in a later version (latest 2.0.13) | 30 Sep 2025 |
| Cross-site scripting (XSS) CVE-2021-24559 | Medium 5.4 | Before 0.7 | Fixed in 0.7 | 16 Jan 2024 |
Read the published descriptions
- CVE-2025-10000, 30 Sep 2025
- The Qyrr - simply and modern QR-Code creation plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the blob_to_file() function in all versions up to, and including, 2.0.7. This makes it possible for authenticated attackers, with Contributor-level access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible. CVE record
- CVE-2021-24559, 16 Jan 2024
- The Qyrr WordPress plugin before 0.7 does not escape the data-uri of the QR Code when outputting it in a src attribute, allowing for Cross-Site Scripting attacks. Furthermore, the data_uri_to_meta AJAX action, available to all authenticated users, only had a CSRF check in place, with the nonce available to users with a role as low as Contributor allowing any user with such role (and above) to set a malicious data-uri in arbitrary QR Code posts, leading to a Stored Cross-Site Scripting issue. CVE record
What to do if you run Qyrr
If you run Qyrr, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Qyrr vulnerabilities
Free. We email you when a new vulnerability is published for Qyrr, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.