VulnTitan VulnTitan Security command center
Plugin Vulnerability Hub
Plugin 1 known issue Latest disclosed Jan 01, 2018

furikake Vulnerabilities

Review known vulnerability records for the WordPress plugin furikake (`furikake`), including severity, CVE references, affected versions, and patch status.

Recent tracked CVEs on this page include CVE-2017-1000434, so operators can jump from disclosure to patch validation without scanning the full feed first.

View on WordPress.org Back to Feed
Known Records
1
High or Critical
0
Patch Coverage
100%
Last Updated
Jan 22, 2024
Related Security Guides

Use these guides while reviewing furikake fixes

Pair this plugin vulnerability hub with practical WordPress hardening, scanner, and patch workflow guidance.

Hardening
WordPress hardening checklist for exposed plugins

Review patch cadence, privileged access, XML-RPC exposure, backups, and monitoring controls.
Plugin Security
WordPress plugin security basics for patch decisions

Use ownership, update testing, least privilege, and removal criteria to reduce plugin risk.
Scanning
WordPress vulnerability scanner buyer's guide

Compare scanner coverage for plugin CVEs, version detection, alert noise, and remediation workflow.
Patch Decision Workflow

How to prioritize furikake remediation

Use the hub as a decision layer before opening individual records: confirm whether the issue has a CVE, whether a fixed version exists, and whether the affected range overlaps production installs.

Search-Ready Records
1
1. Match the Package
Confirm the installed WordPress plugin slug is furikake before acting on any CVE from this cluster.
2. Sort by Severity
Start with 0 high or critical records, then review medium and unrated findings with public references.
3. Check Patch Evidence
1 record include a patch path; verify compatibility before closing the finding.
4. Monitor Gaps
0 records still lack a listed fixed release, so keep this hub in the review queue.
High-Signal Remediation Targets
CVE-2017-1000434 Medium
Vulnerability remediation for furikake

Affected range: Versions up to 0.1.0. Fixed version: 0.1.1.

Priority CVE Quick Links

Fast paths into furikake CVE reports

Start with the highest-signal CVE records for this WordPress plugin before scanning the full vulnerability feed.

Indexed CVEs
1
Tracked CVE Issue Type Affected Versions Fixed Version CVSS
CVE-2017-1000434
furikake <= 0.1.0 - Open Redirect
 Vulnerability Versions up to 0.1.0 0.1.1 CVSS 6.1
CVE-2017-1000434 Medium 0.1.1
CVE-2017-1000434 furikake Vulnerability

furikake <= 0.1.0 - Open Redirect

Coverage Snapshot

What this page helps you verify fast

This hub clusters tracked records for furikake so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.

Patch Visibility
1 record include a published patch path, leaving 0 with no listed safe release yet.
Severity Mix
0 critical and 0 high severity findings.
Recent CVEs
CVE-2017-1000434
Reference Workflow
Jump from the hub into the full report when you need remediation notes, exploit context, CVSS vectors, or source references.
Triage First

Open the records most likely to drive action

These recent records surface the CVE strings, patch cues, and direct report links most operators need first.

Known Vulnerabilities

Reports for furikake

Sorted by latest disclosure date so newly published issues surface first.

Plugin Medium Patched: Yes CVE-2017-1000434
CVE-2017-1000434: furikake <= 0.1.0 - Open Redirect

Wordpress plugin Furikake version 0.1.0 is vulnerable to an Open Redirect The furikake-redirect parameter on a page allows for a redirect to an attacker controlled page classes/Furigana.php: header('location:'.urldecode($_GET['furikake-redirect']));

Published
Jan 01, 2018
Patched Release
0.1.1
Affected Versions
Versions up to 0.1.0
Next Step
Update to 0.1.1 or newer if supported.
Review CVE-2017-1000434 fixed version details Open CVE Reference