ThemeREX Printo Plugin up to 1.11 on WordPress filename control

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.7$0-$5k0.90-

Summaryinfo

A vulnerability identified as problematic has been detected in ThemeREX Printo Plugin up to 1.11 on WordPress. The affected element is an unknown function. The manipulation leads to filename control. This vulnerability is uniquely identified as CVE-2025-69159. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability was found in ThemeREX Printo Plugin up to 1.11 on WordPress and classified as problematic. This issue affects some unknown functionality. The manipulation with an unknown input leads to a filename control vulnerability. Using CWE to declare the problem leads to CWE-98. The PHP application receives input from an upstream component, but it does not restrict or incorrectly restricts the input before its usage in "require," "include," or similar functions. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Unauthenticated Local File Inclusion in Printo <= 1.11 versions.

The weakness was disclosed by Bonds. The advisory is shared at patchstack.com. The identification of this vulnerability is CVE-2025-69159 since 12/29/2025. The exploitation is known to be difficult. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 06/17/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.8
VulDB Meta Temp Score: 6.7

VulDB Base Score: 5.6
VulDB Temp Score: 5.4
VulDB Vector: 🔒
VulDB Reliability: 🔍

CNA Base Score: 8.1
CNA Vector (Patchstack): 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Filename control
CWE: CWE-98
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔒

Timelineinfo

12/29/2025 CVE reserved
06/17/2026 +169 days Advisory disclosed
06/17/2026 +0 days VulDB entry created
06/17/2026 +0 days VulDB entry last update

Sourcesinfo

Advisory: patchstack.com
Researcher: Bonds
Status: Not defined

CVE: CVE-2025-69159 (🔒)
GCVE (CVE): GCVE-0-2025-69159
GCVE (VulDB): GCVE-100-371597

Entryinfo

Created: 06/17/2026 06:00
Changes: 06/17/2026 06:00 (63)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!