CVE-2015-10073 is a critical-severity (CVSS 9.6) Cross-site Scripting (XSS) vulnerability in tinymighty/wiki-seo. A fix is available for tinymighty/wiki-seo — see the affected versions and patch details below.
tinymighty WikiSEO is vulnerable to cross-site scripting via modifyHTML function
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
tinymighty/wiki-seoReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
A vulnerability, which was classified as problematic, was found in tinymighty WikiSEO 1.2.1 on MediaWiki. This affects the function modifyHTML of the file WikiSEO.body.php of the component Meta Property Tag Handler. The manipulation of the argument content leads to cross site scripting. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 1.2.2 is able to address this issue. The patch is named 089a5797be612b18a820f9f1e6593ad9a91b1dba. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-220215.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | tinymighty/wiki-seo | all versions | 1.2.2composer require tinymighty/wiki-seo:^1.2.2 |
Affected Products
wikiseotinymightyDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tinymighty/wiki-seo, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update tinymighty/wiki-seo to 1.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-10073 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2015-10073 in your dependencies?
Find it across Packagist, including transitive dependencies.