Who is affected
You are affected if you run Openwave Messaging Limited Webtop Media Transcoder in your environment. The vulnerability allows an authenticated user to process and convert document types that should be blocked when the Webmail experience is bypassed. The record does not specify which versions are vulnerable or the scope of document types at risk.
How to check whether this touches you
- Search your asset inventory for "Webtop Media Transcoder" or Openwave Messaging Limited products; note all instances and their versions.
- Confirm whether the transcoder is exposed to network ingress beyond your trusted administrative users—check firewall rules, reverse-proxy configurations, and authentication requirements on the service endpoint.
- Query your Openwave Messaging Limited instance or vendor documentation for the running version number; version alone does not confirm safety, as backported fixes may exist outside official release numbers.
- Review access logs to identify which user accounts have authenticated to the transcoder in the past 90 days.
- Examine whether the Webmail interface is the sole intended path to document conversion, or whether direct API or backend access to the transcoder is documented or in use.
What to do
- Immediately: Stop or restrict network access to the Webtop Media Transcoder to authenticated administrative users only, using firewall rules or network segmentation, until you can patch or apply vendor mitigations.
- Establish a patch timeline: Contact Openwave Messaging Limited to confirm whether a patch or mitigation exists; align your deployment schedule with CISA BOD 26-04 risk-based patching guidance and your organisation's asset criticality classification.
- If no patch is available: Evaluate whether you can discontinue use of the product or isolate it further; document this decision and escalate to your information security and business continuity teams.
- Enable logging: Ensure that all authentication events and document conversion requests to the transcoder are logged with sufficient detail to reconstruct user activity; retain logs for at least 90 days.
- Test the fix: Once a vendor update is available, deploy it first to a non-production instance, confirm that document type restrictions are enforced, and then roll out to production.
If you find you were exposed
Exploitation of this vulnerability requires valid authentication, so review your access logs and authentication systems for any user accounts that were compromised or misused during the period between your last security audit and now. If you find evidence of authenticated use that bypassed Webmail controls or processed unexpected document types, retain those logs and escalate to your incident response team for forensic analysis. Assume that any documents processed during the exposure window may have been accessed by an attacker.