CVE-2025-25138
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 Rishi On Page SEO + Whatsapp Chat Button ops-robots-txt allows Stored XSS.This issue affects On Page SEO + Whatsapp Chat Button: from n/a through <= 2.0.0.
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 · high confidenceA CSRF vulnerability in the On Page SEO + Whatsapp Chat Button WordPress plugin (ops-robots-txt) allows attackers to inject malicious scripts through forged requests, resulting in Stored XSS. The plugin lacks proper CSRF token validation on its configuration forms and AJAX endpoints, enabling authenticated administrators to be tricked into submitting crafted requests that persist malicious code.
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.
-
Verify plugin installation and versionIn WordPress admin, go to Plugins > Installed Plugins and look for 'On Page SEO + Whatsapp Chat Button' or 'ops-robots-txt'. Note the installed version number from the plugin details.Affected if The plugin is installed and active, regardless of version (since no safe version is specified, assume all versions are potentially affected)
-
Inspect plugin forms for CSRF tokensNavigate to the plugin settings page in WordPress admin. View the page source (right-click > View Page Source) and search for the form elements. Look for hidden input fields containing 'nonce' or '_wpnonce' within the plugin's configuration forms.Affected if The plugin forms lack _wpnonce or nonce hidden fields, indicating missing CSRF protection
-
Check AJAX endpoint nonce validationAccess the plugin directory via FTP or file manager. Locate the main plugin PHP file and any AJAX handler files. Search for 'wp_ajax_' actions and check if they include wp_verify_nonce(), check_admin_referer(), or wp_nonce_field() calls before processing requests.Affected if AJAX endpoints do not verify nonces before processing form data
-
Identify stored XSS injection pointsIn the plugin settings, locate any fields that accept user input and are stored in the database (options, settings, or custom post types). Check if input is sanitized using functions like esc_html(), esc_attr(), or sanitize_text_field() before saving.Affected if Plugin saves user input without proper sanitization, allowing stored XSS payloads to persist
A user is affected if the On Page SEO + Whatsapp Chat Button plugin is installed and its configuration forms or AJAX endpoints lack server-side nonce/CSRF token validation.
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 nonces/CSRF tokens on all plugin forms and AJAX actions, validate the nonce server-side before processing requests, and use wp_nonce_field() and check_admin_referer() or wp_verify_nonce() for WordPress-native protection.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-25138 — 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-25138 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