CVE-2025-14892
Hardcoded Secret Enables Admin Access in Prime Listing Manager
Publication date: 2026-02-12
Last updated on: 2026-02-12
Assigner: WPScan
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| prime_listing_manager | prime_listing_manager | to 1.1 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': 'CVE-2025-14892 is a critical vulnerability in the Prime Listing Manager WordPress plugin version 1.1 and earlier that allows an attacker to gain administrative access without having any account on the targeted site.'}, {'type': 'paragraph', 'content': 'The vulnerability exists because the plugin uses a hardcoded secret key to generate JSON Web Tokens (JWTs). An attacker can exploit this by forging valid JWTs using the hardcoded secret, which lets them impersonate an admin user.'}, {'type': 'paragraph', 'content': "The attacker creates a JWT with an admin user ID and username, signs it with the hardcoded secret using HMAC-SHA256, and then uses this token in an HTTP POST request to the pluginβs REST API endpoint to reset the admin user's password. This enables the attacker to log in as the admin."}, {'type': 'paragraph', 'content': 'This vulnerability is classified under CWE-269 (Improper Privilege Management) and is part of the OWASP Top 10 category A2: Broken Authentication and Session Management.'}] [1]
How can this vulnerability impact me? :
This vulnerability can have severe impacts as it allows an unauthenticated attacker to gain full administrative access to a WordPress site using the Prime Listing Manager plugin.
- The attacker can reset the password of any admin user, effectively taking over the site.
- Once administrative access is obtained, the attacker can perform unauthorized actions such as modifying content, installing malicious plugins, stealing sensitive data, or disrupting site operations.
- Because no authentication is required, the attack can be performed remotely and without any prior access.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': "This vulnerability can be detected by monitoring for unauthorized HTTP POST requests to the WordPress plugin's REST API endpoint `/wp-json/primlima/v1/user/change-password` that include an Authorization header with a JWT token."}, {'type': 'paragraph', 'content': 'Specifically, you can look for JWT tokens signed with the hardcoded secret key "ilovewordpress" used by the vulnerable Prime Listing Manager plugin.'}, {'type': 'paragraph', 'content': 'A possible detection method is to capture and inspect HTTP requests to the endpoint and verify if the Authorization header contains a JWT token that can be decoded and verified using the secret "ilovewordpress".'}, {'type': 'paragraph', 'content': 'Example commands to detect suspicious activity might include using curl or network monitoring tools to check for such requests.'}, {'type': 'list_item', 'content': 'Use a network capture tool (e.g., tcpdump or Wireshark) to filter HTTP POST requests to `/wp-json/primlima/v1/user/change-password`.'}, {'type': 'list_item', 'content': "Example tcpdump command: `tcpdump -A -s 0 'tcp port 80 or tcp port 443' | grep '/wp-json/primlima/v1/user/change-password'`"}, {'type': 'list_item', 'content': 'Inspect the Authorization header in captured requests for JWT tokens.'}, {'type': 'list_item', 'content': 'Use a JWT decoding tool or script to decode the token and verify if it is signed with the secret "ilovewordpress".'}] [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include disabling or removing the vulnerable Prime Listing Manager WordPress plugin version 1.1 or earlier from your site.
Since no fix is currently known for this vulnerability, preventing access to the vulnerable REST API endpoint is critical.
You can also implement web application firewall (WAF) rules to block unauthorized POST requests to `/wp-json/primlima/v1/user/change-password`.
Additionally, monitor your site for any unauthorized password changes or suspicious administrative logins.
Consider resetting all administrative passwords manually to ensure no attacker has gained access.