dbcve.org
Mail Integration For Office 365 \/ OutlookWordPress extension · Wpo365

CVE-2023-32119

MEDIUM · 6.1 CVSS v3.1 Published 2023-08-23
Fix available
A fix is available. Upgrade to 1.9.1 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Unauth. Reflected Cross-Site Scripting (XSS) vulnerability in WPO365 | Mail Integration for Office 365 / Outlook plugin <= 1.9.0 versions.

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 confidence

An unauthenticated reflected cross-site scripting (XSS) vulnerability exists in the WPO365 Mail Integration for Office 365/Outlook WordPress plugin versions 1.9.0 and below. The vulnerability allows attackers to inject malicious scripts through unsanitized user inputs that are reflected back in the application's response.

MitigationUpgrade the WPO365 plugin to a version newer than 1.9.0. As a temporary measure, implement a Web Application Firewall (WAF) to block XSS attack patterns until the patch can be applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Mail Integration For Office 365 \/ OutlookWordPress extension
Affected:< 1.9.1

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
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify WPO365 plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WPO365 Mail Integration For Office 365 / Outlook' or check the plugin files in /wp-content/plugins/ directory
    Affected if The plugin is not found in the WordPress installation
  2. Check the installed version
    In WordPress admin, go to Plugins > Installed Plugins and find the version number listed under the WPO365 plugin name, or check the plugin header in the main PHP file
    Affected if The version is 1.9.0 or below, or the version cannot be determined and the plugin is present
  3. Confirm the plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and check if the WPO365 plugin shows as 'Active'
    Affected if The plugin is active and version is 1.9.0 or below
  4. Check if mail integration is configured
    Look for WPO365 settings in WordPress admin under Settings > WPO365 Mail or similar menu items, and verify if any mail-related options are enabled
    Affected if The plugin is active and mail integration settings are present and configured

The environment is affected if the WPO365 Mail Integration plugin version 1.9.0 or below is installed and active in WordPress, as the reflected XSS vulnerability exists in unauthenticated user input handling regardless of mail configuration status.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 1.9.1 or later
Fixed in 1.9.1
Interim mitigation

Upgrade the WPO365 plugin to a version newer than 1.9.0. As a temporary measure, implement a Web Application Firewall (WAF) to block XSS attack patterns until the patch can be applied.

Recommended fix High confidence

1.9.1 or later

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the 'WPO365 | Mail Integration for Office 365 / Outlook' plugin
  4. Click 'Update now' if an update is available, or manually download version 1.9.1 from the WordPress plugin repository and upload it
  5. Verify the plugin is updated to version 1.9.1 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mail Integration For Office 365 \/ Outlook Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-32119 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-32119 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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