Cyber Resilience

CVE-2025-8625

Exposed Creds

Published
30 September 2025
Modified
15 April 2026
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0056 44th percentile
Risk Priority 72 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-8625 is a critical-severity Use of Hard-coded Cryptographic Key (CWE-321) vulnerability in Wordpress (inferred from references). Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Private Keys (T1552.004); ranked at the 44th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-12 (Cryptographic Key Establishment and Management) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-8625 is a critical remote code execution vulnerability in the Copypress Rest API plugin for WordPress, affecting versions 1.1 through 1.2. The issue stems from the copyreap_handle_image() function, which falls back to a hard-coded JWT signing key when no secret is defined and fails to restrict file types that can be fetched and saved as attachments. This allows attackers to forge valid JWT tokens, granting elevated privileges and enabling the upload of arbitrary files, such as PHP scripts, directly through the image handler. The vulnerability carries a CVSS v3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) and is associated with CWE-321 (Use of Hard-coded Cryptographic Key).

Unauthenticated attackers can exploit this vulnerability remotely with low complexity and no user interaction required. By crafting a forged JWT token using the known hard-coded signing key, they gain elevated privileges to interact with the image handler endpoint. This enables the upload and execution of malicious files, such as PHP webshells, resulting in full remote code execution on the targeted WordPress site.

Advisories from Wordfence and the Copypress Rest API plugin developers on WordPress.org detail mitigation steps and patch information. Security practitioners should refer to https://www.wordfence.com/threat-intel/vulnerabilities/id/3045c9e5-4095-48e5-8d9d-16a091e69d54?source=cve and https://wordpress.org/plugins/copypress-rest-api/#developers for updates, including available patches and remediation guidance.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

The Copypress Rest API plugin for WordPress is vulnerable to Remote Code Execution via copyreap_handle_image() Function in versions 1.1 to 1.2. The plugin falls back to a hard-coded JWT signing key when no secret is defined and does not restrict…

more

which file types can be fetched and saved as attachments. As a result, unauthenticated attackers can forge a valid token to gain elevated privileges and upload an arbitrary file (e.g. a PHP script) through the image handler, leading to remote code execution.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1552.004 Private Keys Credential Access
Adversaries may search for private key certificate files on compromised systems for insecurely stored credentials.
T1552 Unsecured Credentials Credential Access
Adversaries may search compromised systems to find and obtain insecurely stored credentials.
T1552.001 Credentials In Files Credential Access
Adversaries may search local file systems and remote file shares for files containing insecurely stored credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-31362Shared CWE-321
CVE-2026-9770Shared CWE-321
CVE-2025-35052Shared CWE-321
CVE-2025-56577Shared CWE-321
CVE-2025-24525Shared CWE-321
CVE-2024-11308Shared CWE-321
CVE-2024-52881Shared CWE-321
CVE-2025-27674Shared CWE-321
CVE-2024-35344Shared CWE-321
CVE-2025-58426Shared CWE-321

Affected Assets

Wordpress
—
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Requiring cryptographic keys to be established and managed according to defined requirements prevents developers from embedding static unchangeable keys.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure-SDLC activities such as code review and secret scanning directly prevent embedding static keys.

PR.DS-01 partial match
prevents

Data-at-rest protection policies require proper key management and therefore discourage hard-coded keys.

PR.DS-02 partial match
prevents

Data-in-transit protection similarly depends on non-hard-coded keys for encryption.

PR.PS-01 partial match
prevents

Configuration baselines and reviews can prohibit hard-coded keys in deployed artifacts.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Key-management controls that govern generation, rotation and protection of keys make the use of embedded hard-coded cryptographic keys less likely and easier to detect.

References