Contact us
← Article questionsWhat should we do?

CVEHit Business Advisory by IntegrityLab.ai

What should we do?

Unauthorized administrative actions on WSO2 System REST APIs — CVE-2025-11969: Business Triage

Do Now

  • System owner: update API Manager 4.5.0 subscriptions to U2 update level 32 or higher.
    Proof the update is done
    • Use the row for the installed product and base version.
    • API Manager 4.5.0 subscriptions need U2 update level 32 or higher.
    • Do not copy level 32 onto another row.
    • Subscription updates come through WSO2 Updates.
    • For a community build, apply the public fix linked from the advisory.
      • A version number alone does not confirm that fix.
      • If that public fix cannot be applied, migrate to the latest unaffected version of the same product.
      • No universal replacement release is named.
    • If the base version is in an unknown range, do not mark it fixed.
    • A finished update does not settle earlier changes.
    • Record these fields.
      • Installed product.
      • Base version.
      • Update level after the work.
      • Subscription or community path used.
      • Source of the record.
      • Date checked.
  • Network owner: limit this product's System REST APIs to trusted networks, as a reachability reduction that does not replace the fix.
    What to record
    • Limit the management System REST APIs to trusted networks.
    • This is a reachability reduction, not a vendor patch.
    • APIs created and exposed through the API Manager API Gateway are a different surface.
    • Universal Gateway can need its own fix.
    • The privilege needed to call System REST APIs remains unresolved.
    • If reach is already limited, record that evidence. The product can need the fix even then.
    • Record these fields.
      • Product.
      • Who can reach the System REST APIs.
      • Source of the record.
      • Date checked.
  • Security owner: review existing audit and change records for unexplained administrative actions, including products already updated, and start response if one appears.
    Where to look first
    • Preserve existing records before the update when you still can.
    • Review the period the product was reachable, including products already updated.
    • Include use before the January 26, 2026 advisory. The November 2, 2026 CVE date is a later publication.
    • For API Manager 4.5.0, start with audit.log under API-M_HOME/repository/logs.
    • Gateway API logs do not establish System REST history.
    • Start response even if this CVE is not established as the cause.
    • A later fix does not settle earlier changes.
    • A clean log is not proof of no change.
    • A missing log leaves the question unresolved.
    • Record these fields.
      • Records reviewed.
      • Source of the records.
      • Period covered.
      • Date reviewed.

Do Next

  • System owner: if a base version is unknown, or the community public fix cannot be applied, ask the provider which fix or unaffected version applies.
    What to ask
    • Ask which fix applies to each older unknown base version.
    • Ask which unaffected version of the same product applies when the linked community fix cannot be applied.
    • Do not invent a backport.
    • Do not invent a universal replacement release.
    • Do not treat an unknown package version as a product update level.
    • Record these fields.
      • Product.
      • Base version.
      • Provider answer.
      • Source of the answer.
      • Date checked.

← Back to article questions

How can we help?

Initial enquiries only. Omit passwords, access tokens, security reports or other sensitive information. We’ll arrange secure sharing if needed.

Privacy & data handling ↗. Submitting this form does not authorise an assessment.

Checking enquiry availability…