CVE-2025-30612
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-Site Request Forgery (CSRF) vulnerability in mandegarweb Replace Default Words replace-default-words allows Stored XSS.This issue affects Replace Default Words: from n/a through <= 1.3.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCSRF vulnerability in the Replace Default Words WordPress plugin (≤1.3) allows unauthenticated attackers to trick authenticated administrators into submitting forms that inject malicious JavaScript (Stored XSS) into replacement values, which then executes when viewed by site users.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm plugin installation and versionNavigate to WordPress admin > Plugins and locate 'Replace Default Words' in the installed plugins list. Note the version number displayed next to the plugin name.Affected if The plugin is installed and the version is 1.3 or lower
-
Inspect plugin source code for nonce verificationAccess the plugin files via FTP or file manager (wp-content/plugins/replace-default-words/). Open the main PHP file(s) that handle admin form submissions and search for 'wp_nonce_field' or 'check_admin_referer' function calls.Affected if The plugin code handling admin forms lacks nonce verification logic
-
Examine stored replacement values for XSS payloadsAccess the WordPress database (via phpMyAdmin or WP-CLI). Query the options table for plugin-related settings: SELECT * FROM wp_options WHERE option_name LIKE '%replace_default_words%' or similar. Inspect the stored values for suspicious JavaScript tags (<script>, javascript:, onerror=, etc.).Affected if Stored replacement values contain unescaped HTML or JavaScript code
-
Check for recent unauthorized admin actionsReview WordPress audit logs or activity logs (if available) for admin form submissions to the plugin settings page from your IP. Look for unexpected changes to replacement rules.Affected if Replacement rules were modified without your knowledge or from unexpected IP addresses
If the Replace Default Words plugin is installed at version 1.3 or lower and stores unescaped HTML/JavaScript in replacement values, the environment is vulnerable to this CVE.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement nonce verification on all admin forms and sanitize/escape user input before storing and displaying replacement values to prevent XSS.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30612 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-30612 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data