Relevanssi Plugin/Relevanssi Premium Plugin on WordPress Request authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in Relevanssi Plugin and Relevanssi Premium Plugin on WordPress. The affected element is an unknown function of the component Request Handler. The manipulation results in authorization. This vulnerability is cataloged as CVE-2023-7199. The attack may be launched remotely. There is no exploit available. You should upgrade the affected component.
Details
A vulnerability classified as problematic has been found in Relevanssi Plugin and Relevanssi Premium Plugin on WordPress (WordPress Plugin) (affected version not known). Affected is some unknown functionality of the component Request Handler. The manipulation with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-639. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. This is going to have an impact on confidentiality. CVE summarizes:
The Relevanssi WordPress plugin before 4.22.0, Relevanssi Premium WordPress plugin before 2.25.0 allows any unauthenticated user to read draft and private posts via a crafted request
The weakness was shared 01/29/2024 by Krzysztof Zając. The advisory is shared for download at wpscan.com. This vulnerability is traded as CVE-2023-7199 since 01/02/2024. There are neither technical details nor an exploit publicly available.
Upgrading eliminates this vulnerability. The upgrade is hosted for download at relevanssi.com.
Once again VulDB remains the best source for vulnerability data.
Product
Type
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.2
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.3
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: AuthorizationCWE: CWE-639 / CWE-285 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: relevanssi.com
Timeline
01/02/2024 🔍01/29/2024 🔍
01/29/2024 🔍
05/30/2025 🔍
Sources
Advisory: wpscan.comResearcher: Krzysztof Zając
Status: Confirmed
CVE: CVE-2023-7199 (🔍)
GCVE (CVE): GCVE-0-2023-7199
GCVE (VulDB): GCVE-100-252324
Entry
Created: 01/29/2024 16:56Updated: 05/30/2025 01:38
Changes: 01/29/2024 16:56 (40), 02/21/2024 16:46 (10), 05/30/2025 01:38 (16)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.