Quick answers
- Is CVE-2026-39627 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-39627 being exploited in the wild.
- How severe is CVE-2026-39627?
- Medium severity, with a CVSS score of 4.3, published 8 April 2026.
- Which products and versions are affected?
- WP Royal Ashe <= 2.267.
- Is there a fix for CVE-2026-39627?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-39627 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-39627?
- Check whether you run WP Royal Ashe at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A missing authorization (CWE-862) vulnerability exists in the WP Royal Ashe theme for WordPress through version 2.267. The flaw stems from incorrectly configured access control security levels, which fail to properly validate user permissions before executing certain functions. An attacker authenticated with low-level privileges, such as a Subscriber, can exploit this vulnerability over the network to perform actions typically reserved for higher-privileged users. The issue is resolved in version 2.268.
Affected products
- WP Royal Ashe <= 2.267
Timeline
- 2026-01-13: other: Vulnerability reported by researcher
- 2026-02-12: advisory: Patchstack advisory published
- 2026-04-08: disclosed: CVE published