CVE-2019-11633: HoneyPress through 2016-09-27 can be fingerprinted by attackers because of the ingrained unique www.atxsec.com

Q: How do I fix CVE-2019-11633?

honeypress: upgrade to newer than 2016-09-27. Exact commands for each OS are on this page.

Q: Is CVE-2019-11633 being exploited?

CVE-2019-11633 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2019-11633 affect?

CVE-2019-11633 affects honeypress. Severity is high (CVSS 7.5). HoneyPress through 2016-09-27 can be fingerprinted by attackers because of the ingrained unique www.atxsec.com and ayylmao.wpengine.com hostnames within the fake WordPress templates. This allows attackers to discover and avoid this honeypot

Q: How urgent is CVE-2019-11633?

Priority 49/100. High severity; Remotely exploitable, no login, no user action

This month

HIGH 7.5REMOTEUPGRADE

CVE-2019-11633 is a high-severity flaw (CVSS 7.5) affecting honeypress. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

HoneyPress through 2016-09-27 can be fingerprinted by attackers because of the ingrained unique www.atxsec.com and ayylmao.wpengine.com hostnames within the fake WordPress templates. This allows attackers to discover and avoid this honeypot system.

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.4% (top 27%)
CISA exploited list	No
Weakness	CWE-200
Published	2019-05-01
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: honeypress project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2019-05-01 14:29 UTCPublished CVE record published
2026-06-17 02:13 UTCUpdated Record last modified

honeypress project honeypress UPGRADE

Affected: <= 2016-09-27

Fixed in: newer than 2016-09-27

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy honeypress || rpm -q honeypress || honeypress --version

2. UPGRADE to newer than 2016-09-27 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade honeypress

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade honeypress

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-11633?

honeypress: upgrade to newer than 2016-09-27. Exact commands for each OS are on this page.

Is CVE-2019-11633 being exploited?

CVE-2019-11633 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-11633 affect?

CVE-2019-11633 affects honeypress. Severity is high (CVSS 7.5). HoneyPress through 2016-09-27 can be fingerprinted by attackers because of the ingrained unique www.atxsec.com and ayylmao.wpengine.com hostnames within the fake WordPress templates. This allows attackers to discover and avoid this honeypot

How urgent is CVE-2019-11633?

Priority 49/100. High severity; Remotely exploitable, no login, no user action

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs