NVD / CVE Program· CNA jpcert

CVE-2022-43504: Improper authentication vulnerability in WordPress versions prior to 6.0.3 allows a remote unauthenticated attacker to obtain the email addr

Noroxi assessment

Priority: Monitor (action score 21/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 1.4% (FIRST EPSS); higher than 74.3% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to CISA the attack is automatable: targets can be found by mass scanning.
Fixed version: wordpress (Debian:11) 5.7.8+dfsg1-0+deb11u1; wordpress (Debian:12) 6.0.3+dfsg1-1.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to wordpress (Debian:11) 5.7.8+dfsg1-0+deb11u1; wordpress (Debian:12) 6.0.3+dfsg1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Improper authentication vulnerability in WordPress versions prior to 6.0.3 allows a remote unauthenticated attacker to obtain the email address of the user who posted a blog using the WordPress Post by Email Feature. The developer also provides new patched releases for all versions since 3.7.

MediumCVSS 5.3 · v3.1—No exploit Fix available

DSA-5279-1

Published: Dec 5, 2022
Updated: Jun 17, 2026
EPSS: 1.4% · 74th percentile
CWE: CWE-287

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 21 / 40 · 5.3 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 1.4%

CISA SSVC decision

Exploitation: none
Automatable: yes
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

Is WordPress on your site?

WP Lens reads your site's plugin, theme and WordPress versions from the outside and matches them to known vulnerabilities. Works without an account.

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
wordpress	wordpress	cpe:2.3:a:wordpress:wordpress

Using wordpress? Add it to your stack and be the first to know about CVEs like this one. (WordPress)

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

wordpress wordpressbefore 3.7.40
wordpress wordpress3.8 and later · before 3.8.40
wordpress wordpress3.9 and later · before 3.9.39
wordpress wordpress4.0 and later · before 4.0.37
wordpress wordpress4.1 and later · before 4.1.37
wordpress wordpress4.2 and later · before 4.2.34
wordpress wordpress4.3 and later · before 4.3.30
wordpress wordpress4.4 and later · before 4.4.29
wordpress wordpress4.5 and later · before 4.5.28
wordpress wordpress4.6 and later · before 4.6.25
wordpress wordpress4.7 and later · before 4.7.25
wordpress wordpress4.8 and later · before 4.8.21
wordpress wordpress4.9 and later · before 4.9.22
wordpress wordpress5.0 and later · before 5.0.18
wordpress wordpress5.1 and later · before 5.1.15
wordpress wordpress5.2 and later · before 5.2.17
wordpress wordpress5.3 and later · before 5.3.14
wordpress wordpress5.4 and later · before 5.4.12
wordpress wordpress5.5 and later · before 5.5.11
wordpress wordpress5.6 and later · before 5.6.10

Versions reported by the vendor

Affected version ranges reported by the assigning authority (jpcert). Independent of NVD's CPE analysis and usually ahead of it.

WordPress.org WordPress
- versions prior to 6.0.3affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:11	wordpress	before 5.7.8+dfsg1-0+deb11u1	5.7.8+dfsg1-0+deb11u1
Debian:12	wordpress	before 6.0.3+dfsg1-1	6.0.3+dfsg1-1

Same product

wordpress: all records

Other highest-scoring records for the same primary product.

CVE-2026-87902An unauthenticated attacker can make `get_page_template()` page-template resolution include a chosen readable local `.php` file outside the KEV
91Now
CVE-2026-63030WordPress < 7.0.2 - REST API batch-route confusion and SQL injection issue leading to Remote Code ExecutionKEV
72This week
CVE-2026-119977WordPress Core 4.7.0 - 7.1.3 - Unauthenticated Upgrade-Window Staged-Installer Remote Code ExecutionKEV
62This week

Published before and after this one in the same product

← EarlierCVE-2022-43497Dec 5, 2022 · Cross-site scripting vulnerability in WordPress versions prior to 6.0.3 allows a remote unauthenticated attacker to inject an arbitrary scri
24Monitor
← EarlierCVE-2022-43500Dec 5, 2022 · Cross-site scripting vulnerability in WordPress versions prior to 6.0.3 allows a remote unauthenticated attacker to inject an arbitrary scri
24Monitor
Later →CVE-2022-3590Dec 14, 2022 · WP <= 6.1.1 - Unauthenticated Blind SSRF via DNS Rebinding
24Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
debian:wordpress	6.0.3+dfsg1-1 · Debian:12	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

WordPressHackerOne · paid

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-22-0719 · Dec 5, 2022(WordPress Eklenti Zafiyeti)

All national notices →

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: low · data can be read
Integrity: none
Availability: none

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: Low
Integrity impact: None
Availability impact: None

Weakness class (CWE)

CWE-287 · Improper Authentication

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

nvd-primary

Root cause

Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.

The bug in code

The whole CWE-287 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1app.use("/admin", requireSession, adminRouter);
2

3// Route added later skips the middleware
4app.post("/admin-api/config", updateConfig);

Fixed

1const admin = express.Router();
2admin.use(requireSession, requireRole("admin"));
3

4admin.post("/config", updateConfig);
5app.use("/admin", admin);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Change log

Fix✗ → ✓Sep 28, 2026, 10:48 PM UTC

For records you follow, these changes also arrive as notifications. →

References

jvn.jp/en/jp/JVN09409909/index.html

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records