This demo uses made-up containers.Get exploitwatch on GitHub
exploitwatch

Containers ›

wordpress

Image
docker.io/library/wordpress:apache 776f72647072
State
running
Exposure
Open to the internet (set by label exploitwatch.exposure).
Last looked
2026-11-22 14:28 UTC · its activity ›

Needs action

P1 · wordpress: wordpress bug

wp2shell: update the WordPress site now. Your site is on 6.9.4, even though the image is newer, because WordPress updates itself in the volume.

Why: Attackers are using this bug and wordpress is open to the internet.

Details
Package
wordpress 6.9.4
Fix
fixed in 6.9.5
Priority
P1: KEV · internet exposed
Severity
high · known exploited (KEV) · EPSS 0.620
Image
docker.io/library/wordpress:apache
Not a problem here?

Hides it from your phone and the Overview until it gets more urgent. You can undo this on the container's page.

Your answers

Fill in what Docker can't show. Saving starts a new scan.

Who can reach it?

Now: Open to the internet (set by label exploitwatch.exposure).

Does it read files or traffic from outside?

Files someone else made, like a downloaded video, are riskier to open.

How does it get updates?