CVE-2025-69099
BaseFortify
Publication date: 2026-01-22
Last updated on: 2026-01-28
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| fuelthemes | north_wp | From 5.7.5|end_including=5.7.5 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-502 | The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-69099 is a PHP Object Injection vulnerability in the WordPress North Theme (versions up to 5.7.5). It allows an attacker with contributor or developer privileges to inject malicious code by exploiting deserialization of untrusted data, potentially leading to code injection, SQL injection, path traversal, denial of service, and other attacks if a suitable PHP Object Injection POP chain is present. [1]
How can this vulnerability impact me? :
This vulnerability can allow attackers to execute arbitrary code, perform SQL injection, traverse paths, cause denial of service, and carry out other malicious actions on affected WordPress sites using the North Theme. This can compromise the security and availability of the website and its data. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection can be performed by monitoring for exploitation attempts targeting the WordPress North Theme versions up to 5.7.5, specifically looking for PHP Object Injection attack patterns. Patchstack provides mitigation rules that can help identify and block such attacks. However, no specific detection commands are provided in the available resources. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying the Patchstack mitigation rule that blocks attacks exploiting this vulnerability until an official patch is released. Additionally, restricting contributor or developer privileges can reduce the risk of exploitation. Using automated protection solutions from Patchstack is also recommended to safeguard affected websites. [1]