CVE-2025-14464
Sensitive Information Exposure in WordPress PDF Resume Parser Plugin
Publication date: 2026-01-14
Last updated on: 2026-01-14
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| kiwicommerce | pdf_resume_parser | to 1.0 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-200 | The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability in the PDF Resume Parser WordPress plugin (up to version 1.0) allows unauthenticated attackers to access an AJAX action handler that exposes SMTP configuration data, including credentials such as username and password. This happens because the plugin registers this AJAX handler without authentication, enabling attackers to extract sensitive SMTP credentials from the WordPress configuration. These credentials could then be used to compromise email accounts or gain unauthorized access to other systems using the same credentials.
How can this vulnerability impact me? :
This vulnerability can lead to sensitive information exposure, specifically SMTP credentials. An attacker who exploits this can obtain the username and password for SMTP accounts, potentially compromising email accounts. This could allow unauthorized sending or interception of emails, phishing, or further attacks on other systems that use the same credentials, leading to broader security breaches.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring for unauthorized AJAX requests to the PDF Resume Parser plugin's AJAX action handler that is accessible without authentication. Specifically, you can look for HTTP POST requests to the WordPress admin-ajax.php endpoint with the action parameter related to the PDF Resume Parser plugin. Additionally, inspecting logs for suspicious access patterns or attempts to extract SMTP configuration data is recommended. Since the plugin uses shell_exec() to run the pdftotext command on uploaded PDFs, you can also monitor for unusual pdftotext executions or command injection attempts. Commands to detect such activity might include: 1) Using web server logs to grep for AJAX calls: `grep 'admin-ajax.php' /var/log/apache2/access.log | grep 'action=pdfrp'` (replace 'pdfrp' with the actual action name if known). 2) Monitoring running processes or command history for unexpected pdftotext executions: `ps aux | grep pdftotext` or `grep pdftotext ~/.bash_history`. 3) Using intrusion detection systems or web application firewalls to alert on unauthenticated AJAX requests accessing sensitive plugin actions. Note: The exact AJAX action name is not specified in the provided resources, so adjust the search accordingly. [2]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability exposes sensitive SMTP credentials to unauthenticated attackers, which could lead to unauthorized access to email accounts and potentially other systems. This exposure of sensitive information could result in non-compliance with data protection regulations such as GDPR and HIPAA, which require safeguarding of sensitive data and credentials to protect user privacy and security. However, specific impacts on compliance are not detailed in the provided resources. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Disable or deactivate the PDF Resume Parser plugin until a patch or update is available. 2) Restrict access to the AJAX action handler by requiring authentication or implementing proper capability checks to prevent unauthenticated users from accessing sensitive SMTP configuration data. 3) Review and update SMTP credentials that may have been exposed to prevent unauthorized access. 4) Monitor your system and logs for any suspicious activity related to this vulnerability. 5) Apply any available security patches or updates from the plugin developer as soon as they are released. 6) Consider implementing additional security measures such as web application firewalls to block unauthorized AJAX requests. [2]