Security readout for executives and security teams
Plain-English summary
This affects the WordPress Security, Antivirus, Firewall – S.A.F plugin through version 2.3.5. The plugin can trust a request header for the visitor IP, so a blocked user may appear to come from another IP and bypass login restrictions. It is a medium-severity control bypass, not a data-theft or code-execution issue in the supplied evidence.
Executive priority
Treat as a moderate-priority WordPress hardening issue. It can weaken a security plugin’s access controls, especially on externally reachable login pages, but supplied evidence does not indicate code execution, data exposure, or known active exploitation.
Technical view
The issue is CWE-348: insufficient verification of the source used for IP address data. CVE data says the plugin can use X-Forwarded-For for request logging and login restrictions, allowing a supplied IP value to influence protection decisions. CVSS 3.1 is 5.3: network reachable, low complexity, unauthenticated, no user interaction, integrity impact only.
Likely exposure
Public WordPress sites running Security, Antivirus, Firewall – S.A.F versions up to and including 2.3.5 are the relevant exposure. Risk is greatest where the plugin’s IP blocking or login restriction features are relied on as a security control.
Exploitation context
The source bundle does not show CISA KEV listing or other evidence of active exploitation. The described attack condition is unauthenticated and remote, but impact is limited to bypassing IP-based protection decisions and corrupting request logging assumptions.
Researcher notes
Primary evidence is the CVE/Wordfence description and a WordPress Trac code reference for IP handling. The bundle does not provide a named fixed version, patch diff, or exploitation telemetry, so remediation should be verified against current vendor guidance.
Mitigation direction
- Inventory WordPress sites for the S.A.F plugin and installed version.
- Check vendor or WordPress plugin guidance for a fixed release before upgrading.
- Disable or remove the plugin where it is not required.
- Do not rely on this plugin alone for IP-based login protection.
- Use trusted edge controls for client IP handling where applicable.
Validation and detection
- Confirm whether any WordPress site runs S.A.F version 2.3.5 or earlier.
- Review plugin settings for IP blocking, login restrictions, or request logging reliance.
- Review authentication logs for suspicious access after blocked-IP controls should have applied.
- Check whether compensating controls enforce client IP trust at the reverse proxy or WAF.
- Document whether a vendor-fixed version or replacement control is deployed.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-348: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-4529 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N3.91.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use of Less Trusted Source
Use of Less Trusted Source represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.