← console
voxell vciy

CVE-2022-4346: All In One WP Security & Firewall < 5.1.3 - Configuration Leak

ROUTINE

Telemetry drift only. No threshold crossed and no authority ruling changed.

CVE record, CISA KEV and EPSS as of 2026-10-18.

CVEs like this one computed, by meaning

What to do now held facts and links

  1. Upgrade to 5.1.3 or later CVE record
  2. Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
  3. Check your version against the ranges this record publishes.

What it is stated by the CNA

The All-In-One Security (AIOS) WordPress plugin before 5.1.3 leaked settings of the plugin publicly, including the used email address.

weakness
CWE-552 Files or Directories Accessible to External Parties
affected
Unknown All-In-One Security (AIOS)
published ranges
updraftplus all-in-one security < 5.1.3
fixed in
5.1.3
assigned by
WPScan
published
2023-01-23

check us wpscan.com

Exploit code held, dated

exploit code
None held in the PoC-in-GitHub feed. A public repository changes this brief.

What moved held, dated

dateEPSSevent
24 Jan 20230.00885
7 Mar 20230.00046scoring model v2023.03.01
8 Mar 20230.00046
2 May 20230.00048
17 Mar 20250.00148scoring model v2025.03.14
21 Nov 20250.00146
24 Jan 20260.0039
31 Jan 20260.00254
15 Jun 20260.00658scoring model v2026.06.15

24 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.

Outside the record researched, cited

This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.

Sign in to add the researched section

What would change this brief held, dated

CISA KEV
Not listed in the catalogue we hold. A listing changes this brief.
exploit probability
0.01 on 2026-06-15 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
fix
Held: 5.1.3. A newer fix from the CNA or OSV changes this brief.

Watch this CVE What counts as a move

How to check this

Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:

SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2022-4346', '2026-10-30T23:59:59.999999Z', now());