CVE-2025-30620
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 coderscom WP Odoo Form Integrator wp-odoo-form-integrator allows Stored XSS.This issue affects WP Odoo Form Integrator: from n/a through <= 1.1.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 · moderate confidenceA Cross-Site Request Forgery (CSRF) vulnerability in the WP Odoo Form Integrator WordPress plugin allows attackers to craft malicious requests that result in Stored XSS. The lack of proper CSRF protection enables attackers to trick authenticated administrators into submitting forms that inject malicious scripts into the plugin's stored data, which then executes when viewed by other 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.
-
Verify WP Odoo Form Integrator is installedNavigate to WordPress admin > Plugins > Installed Plugins and search for 'Odoo Form Integrator' or 'wp-odoo-form-integrator'. Alternatively, check the /wp-content/plugins/ directory for a folder named 'wp-odoo-form-integrator' or similar.Affected if The plugin folder exists in the WordPress plugins directory.
-
Check the installed plugin versionIn WordPress admin > Plugins, find the WP Odoo Form Integrator entry and locate the version number displayed below the plugin name. Compare this to any known fixed version from the plugin changelog or security advisory.Affected if The installed version lacks CSRF protection mechanisms (nonces) on form submissions.
-
Confirm the plugin is activeIn WordPress admin > Plugins, verify that WP Odoo Form Integrator shows as 'Active' rather than 'Inactive' or 'Must-Use'.Affected if The plugin is active and processing form submissions.
-
Inspect stored form data for injected scriptsAccess the WordPress database (via phpMyAdmin or wp-cli) and query the plugin's custom tables (typically wp_odoo_form_* or similar) for stored form entries. Look for script tags, javascript: URLs, onload/onerror attributes, or encoded payloads in form fields.Affected if The database contains unexpected script tags or HTML in stored form data that could execute when viewed.
-
Review recent admin form submissionsCheck WordPress activity logs, server access logs, or the plugin's own logs for recent form submissions from the admin area. Look for rapid or批量 submissions that may indicate CSRF exploitation attempts.Affected if Form submissions were made without proper nonce validation or from unexpected IP addresses.
A user is affected if the WP Odoo Form Integrator plugin is installed, active, and lacks CSRF protection, allowing injected scripts to be stored in the database and execute when viewed by other users.
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 anti-CSRF tokens (nonces) on all form submissions and ensure all stored data is properly sanitized before output using WordPress sanitization functions to prevent XSS execution.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30620 — 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-30620 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