Tagregator Plugin 0.6 on WordPress Add New Title Stored cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Tagregator Plugin 0.6 on WordPress. It has been rated as problematic. Affected is an unknown function of the component Add New. Performing a manipulation of the argument Title results in cross site scripting (Stored). This vulnerability is cataloged as CVE-2018-10752. It is possible to initiate the attack remotely. Furthermore, there is an exploit available.
Details
A vulnerability classified as problematic has been found in Tagregator Plugin 0.6 on WordPress (WordPress Plugin). This affects an unknown function of the component Add New. The manipulation of the argument title with an unknown input leads to a cross site scripting vulnerability (Stored). CWE is classifying the issue as CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. This is going to have an impact on integrity. The summary by CVE is:
The Tagregator plugin 0.6 for WordPress has stored XSS via the title field in an Add New action.
The bug was discovered 05/05/2018. The weakness was shared 05/05/2018 (Website). The advisory is shared at pastebin.com. This vulnerability is uniquely identified as CVE-2018-10752 since 05/04/2018. It is possible to initiate the attack remotely. The successful exploitation requires a authentication. It demands that the victim is doing some kind of user interaction. Technical details and a public exploit are known. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept.
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 Exploit-DB (45225). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.6VulDB Meta Temp Score: 3.5
VulDB Base Score: 2.4
VulDB Temp Score: 2.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.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: 🔍
NVD Base Score: 🔍
Exploiting
Name: StoredClass: Cross site scripting / Stored
CWE: CWE-79 / CWE-94 / CWE-74
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
Timeline
05/04/2018 🔍05/04/2018 🔍
05/05/2018 🔍
05/05/2018 🔍
05/05/2018 🔍
08/26/2025 🔍
Sources
Advisory: pastebin.comStatus: Not defined
CVE: CVE-2018-10752 (🔍)
GCVE (CVE): GCVE-0-2018-10752
GCVE (VulDB): GCVE-100-117369
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 05/05/2018 17:25Updated: 08/26/2025 19:18
Changes: 05/05/2018 17:25 (59), 02/02/2020 15:12 (4), 08/26/2025 19:18 (19)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.