WP Blogs Planetarium Plugin up to 1.0 on WordPress Setting cross-site request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in WP Blogs Planetarium Plugin up to 1.0 on WordPress and classified as problematic. The impacted element is an unknown function of the component Setting Handler. This manipulation causes cross-site request forgery. This vulnerability is registered as CVE-2023-6532. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability has been found in WP Blogs Planetarium Plugin up to 1.0 on WordPress (WordPress Plugin) and classified as problematic. Affected by this vulnerability is an unknown part of the component Setting Handler. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. The CWE definition for the vulnerability is CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. As an impact it is known to affect integrity. The summary by CVE is:
The WP Blogs' Planetarium WordPress plugin through 1.0 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged in admin change them via a CSRF attack
The weakness was published 01/08/2024 by Daniel Ruf. It is possible to read the advisory at wpscan.com. This vulnerability is known as CVE-2023-6532 since 12/05/2023. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-58763). Be aware that VulDB is the high quality source for vulnerability data.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.6VulDB Meta Temp Score: 6.5
VulDB Base Score: 4.3
VulDB Temp Score: 4.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
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: Cross-site request forgeryCWE: CWE-352 / CWE-862 / CWE-863
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
12/05/2023 🔍01/08/2024 🔍
01/08/2024 🔍
06/18/2025 🔍
Sources
Advisory: wpscan.comResearcher: Daniel Ruf
Status: Not defined
CVE: CVE-2023-6532 (🔍)
GCVE (CVE): GCVE-0-2023-6532
GCVE (VulDB): GCVE-100-250015
EUVD: 🔍
Entry
Created: 01/08/2024 21:01Updated: 06/18/2025 22:13
Changes: 01/08/2024 21:01 (40), 01/25/2024 15:48 (11), 06/18/2025 20:43 (16), 06/18/2025 22:13 (1)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.