Word Replacer Vulnerabilities

Review known vulnerability records for the WordPress plugin Word Replacer (`word-replacer`), including severity, CVE references, affected versions, and patch status.

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

View on WordPress.org Back to Feed

Known Records

High or Critical

Patch Coverage

100%

Last Updated

Jun 01, 2026

Coverage Snapshot

What this page helps you verify fast

This hub clusters every indexed record for Word Replacer 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-2026-3620

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.

CVE-2026-3620 Medium No patch listed

Word Replacer <= 0.4 - Authenticated (Administrator+) Stored Cross-Site Scripting via 'Replacement' Parameter

The Word Replacer plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'replacement' parameter in all versions up to, and including, 0.4. This is due to insufficient inp...

Published

Jun 01, 2026

Patch Status

Not published

Open Full Report

Known Vulnerabilities

Reports for Word Replacer

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

Plugin Medium Patched: No CVE-2026-3620

Word Replacer <= 0.4 - Authenticated (Administrator+) Stored Cross-Site Scripting via 'Replacement' Parameter

The Word Replacer plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'replacement' parameter in all versions up to, and including, 0.4. This is due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, w...

Published

Jun 01, 2026

Patched Release

Not published

Affected Versions

Versions up to 0.4

Next Step

Open the full report for remediation notes and references.

Open Full Report Open CVE Reference