Is CVE-2026-39559 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-39559 being exploited in the wild.

How severe is CVE-2026-39559?

High severity, with a CVSS score of 8.1, published 17 June 2026.

Which products and versions are affected?

Code Supply Co. Uppercase < 1.2.2.

Is there a fix for CVE-2026-39559?

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-39559 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-39559?

Check whether you run Code Supply Co. Uppercase 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.

CVE-2026-39559: codesupplyco Uppercase Local File Inclusion

Q: Is there a fix for CVE-2026-39559?

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.

Q: How is CVE-2026-39559 attacked?

It is attacked over the network, in a web application.

Q: Am I affected by CVE-2026-39559?

Check whether you run Code Supply Co. Uppercase 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.

CVE-2026-39559 · Severity: high · CVSS 8.1 · Published 2026-06-17

The Uppercase theme for WordPress is vulnerable to a security flaw that allows unauthorized users to access sensitive files on the web server. By exploiting this, an attacker could view configuration files containing database credentials, potentially leading to a full takeover of the website and its data. Website administrators should update the theme to version 1.2.2 or later immediately to resolve this risk.

Vendors: Code Supply Co..

Quick answers

Is CVE-2026-39559 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-39559 being exploited in the wild.
How severe is CVE-2026-39559?: High severity, with a CVSS score of 8.1, published 17 June 2026.
Which products and versions are affected?: Code Supply Co. Uppercase < 1.2.2.
Is there a fix for CVE-2026-39559?: 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-39559 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-39559?: Check whether you run Code Supply Co. Uppercase 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 Local File Inclusion (LFI) vulnerability exists in the Uppercase theme for WordPress (versions < 1.2.2) due to improper control of filenames in PHP include/require statements (CWE-98). An unauthenticated remote attacker can exploit this by sending crafted requests to include local files from the server. Successful exploitation can lead to the disclosure of sensitive information, such as the wp-config.php file, which contains database credentials and security keys. While the attack vector is network-based and requires no privileges, the CVSS assessment indicates high complexity, likely due to specific environmental requirements or configuration needs to trigger the inclusion. The issue is resolved in version 1.2.2.

Affected products

codesupplyco Uppercase < 1.2.2

Timeline

2026-02-07: other: Vulnerability reported by researcher João Pedro S Alcântara
2026-04-08: advisory: Initial advisory published by Patchstack
2026-06-17: disclosed: CVE published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.