Cross-Site Request Forgery (CSRF) in WordPress More Fields Plugin (CVE-2016-20083)
Summary
Vulnerability in WordPress More Fields Plugin (CVE-2016-20083). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
WordPress More Fields Plugin 2.1 contains a cross-site request forgery vulnerability that allows attackers to perform unauthorized actions by disabling CSRF token validation. Attackers can craft malicious web pages that trick logged-in administrators into adding or deleting custom fields and boxes on the Write/Edit page via POST and GET requests to the options-general.php endpoint.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2016-20083 has been found in WordPress More Fields Plugin.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "WordPress More Fields Plugin CVE-2016-20083" on the vendor's site.
CVE-2016-20083 (WordPress More Fields Plugin) — CWE-352 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
CSRF (CWE-352) exists in WordPress More Fields Plugin.
Check the vendor advisory for the affected versions of WordPress More Fields Plugin.
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで WordPress More Fields Plugin を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web disclosure@vulncheck.com
- web disclosure@vulncheck.com
- web disclosure@vulncheck.com
- web nvd.nist.gov
- web github.com