CVE-2024-49337
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 · uneditedIBM OpenPages with Watson 8.3 and 9.0 IBM OpenPages is vulnerable to HTML injection, caused by improper validation of user-supplied input of text fields used to construct workflow email notifications. A remote authenticated attacker could exploit this vulnerability using HTML tags in a text field of an object to inject malicious script into an email which would be executed in a victim's mail client within the security context of the OpenPages mail message. An attacker could use this for phishing or identity theft attacks.
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 confidenceIBM OpenPages is vulnerable to HTML injection in workflow email notifications. Text fields used to construct email content are not properly sanitized, allowing authenticated attackers to inject malicious HTML/script tags. When users receive workflow notification emails, the injected code executes within the security context of the mail client, enabling phishing and identity theft attacks.
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>= 8.3, < 8.3.0.3>= 9.0, < 9.0.0.5CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify IBM OpenPages versionCheck the installed version of IBM OpenPages with Watson in the product documentation, about page, or version info endpoint. Common locations include the IBM OpenPages administration console or system information panel.Affected if The installed version is 8.3.0.0 through 8.3.0.2, or 9.0.0.0 through 9.0.0.4 (i.e., >= 8.3 but < 8.3.0.3, or >= 9.0 but < 9.0.0.5)
-
Confirm workflow email notifications are enabledAccess the IBM OpenPages administration interface and navigate to the workflow configuration settings to determine whether email notifications are turned on for workflows.Affected if Workflow email notifications are enabled in the OpenPages environment
-
Review workflow email template configurationIn the OpenPages admin console, examine the workflow email notification templates and identify which text fields are used to populate email content (such as task titles, descriptions, or custom field values).Affected if The email templates include user-editable text fields that get inserted directly into email content without apparent sanitization
-
Check for untrusted user input in workflow fieldsReview which OpenPages users have permission to modify workflow-related text fields (such as Object Manager fields, custom field values, or workflow task descriptions) that feed into email notifications.Affected if Authenticated users with limited privileges can modify text fields that appear in workflow email notifications
The environment is affected if IBM OpenPages with Watson is installed at a version between 8.3.0.0-8.3.0.2 or 9.0.0.0-9.0.0.4 and workflow email notifications are enabled with user-accessible text fields included in the email content.
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.
dbcve · scoped8.3.0.39.0.0.5
Implement strict input validation and output encoding for all text fields used in workflow email notifications. Sanitize HTML/script tags from user-supplied content before embedding in emails.
IBM OpenPages With Watson 8.3.0.3 or 9.0.0.5 (depending on your current major version)
- 1. Identify the current installed version of IBM OpenPages With Watson by checking the system configuration or About section
- 2. If running version 8.3.0.0 through 8.3.0.2, plan an upgrade to version 8.3.0.3
- 3. If running version 9.0.0.0 through 9.0.0.4, plan an upgrade to version 9.0.0.5
- 4. Review IBM's upgrade documentation and release notes for the target version before proceeding
- 5. Perform a full backup of the current system including database and configuration files
- 6. Schedule a maintenance window as upgrades typically require system downtime
- 7. Execute the upgrade process following IBM's official upgrade procedures
- 8. After upgrade, verify the version number has been updated correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49337 — 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-2024-49337 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