CVE-2018-5361 WPGlobus plugin Stored XSS & CSRF security vulnerability
High 8.8
Published
Updated
Check this codebase for CVE-2018-5361 and fix it if it is affected.
What it is: CVE-2018-5361 is a high-severity vulnerability in n/a, published on 12 Jan 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-5361 in the wild and no public exploit code.
Affected packages and fixed versions:
- wpglobus/wpglobus (Packagist): affected all versions; fixed in 1.9.7
- wpglobus/wpglobus (Packagist): affected all versions; fixed in 1.9.7
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2018-5361/ (Markdown: https://insights.sbomify.com/CVE-2018-5361/index.md)
Cross-site request forgery in WPGlobus plugin allows attackers to modify WordPress settings via options.php.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2018-5361?
CVE-2018-5361 is a high-severity vulnerability in n/a, published on 12 Jan 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
The WPGlobus plugin 1.9.6 for WordPress has CSRF via wp-admin/options.php.
Weakness: CWE-352
Which versions are affected by CVE-2018-5361?
2 open source packages ship an affected version, including wpglobus/wpglobus. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
wpglobus/wpglobus Packagist | All versions | 1.9.7 |
wpglobus/wpglobus Packagist | All versions | 1.9.7 |
Products include Wpglobus Wpglobus.
How do I fix CVE-2018-5361?
Upgrade wpglobus/wpglobus to 1.9.7 or later.
Is CVE-2018-5361 being exploited?
There is no known exploitation of CVE-2018-5361 in the wild and no public exploit code.
Other vulnerabilities in n/a
- CVE-2018-5362 WPGlobus plugin Stored XSS & CSRF security vulnerability
- CVE-2018-5363 WPGlobus plugin Stored XSS & CSRF security vulnerability
- CVE-2018-5364 WPGlobus plugin Stored XSS & CSRF security vulnerability
- CVE-2018-5365 WPGlobus plugin Stored XSS & CSRF security vulnerability
- CVE-2018-5366 WPGlobus plugin Stored XSS & CSRF security vulnerability
Sources
Also known as GHSA-6fxc-v8wq-849g.