CVE-2018-10752: The Tagregator plugin 0.6 for WordPress has stored XSS via the title field in an Add New action.

This month

MEDIUM 4.8DOWNGRADE

CVE-2018-10752 is a medium-severity flaw (CVSS 4.8) affecting tagregator. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Tagregator plugin 0.6 for WordPress has stored XSS via the title field in an Add New action.

Why this priority

Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	4.8 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	High
User interaction	Required
EPSS exploit chance	1.8% (top 21%)
CISA exploited list	No
Weakness	CWE-79
Published	2018-05-05
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: tagregator project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2018-05-05 02:29 UTCPublished CVE record published
2026-06-17 01:34 UTCUpdated Record last modified

tagregator project tagregator DOWNGRADE

Affected: 0.6

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.6

1. Check installed version

apt-cache policy tagregator || rpm -q tagregator || tagregator --version

2. No fixed release: DOWNGRADE to a release before 0.6 (Debian / Ubuntu)

apt-cache madison tagregator sudo apt install tagregator=<VERSION_BEFORE_0.6> sudo apt-mark hold tagregator

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list tagregator sudo dnf downgrade tagregator-<VERSION_BEFORE_0.6> sudo dnf versionlock add tagregator

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Exploit-DB: WordPress Plugin Tagregator 0.6 - Cross-Site Scripting

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2018-10752?

tagregator: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2018-10752 being exploited?

CVE-2018-10752 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2018-10752 affect?

CVE-2018-10752 affects tagregator. Severity is medium (CVSS 4.8). The Tagregator plugin 0.6 for WordPress has stored XSS via the title field in an Add New action.

How urgent is CVE-2018-10752?

Priority 41/100. Public exploit reference

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs