CVE-2022-23305SQL injection in JDBC Appender in Apache Log4j V1
Updated under an hour ago ()
Does this affect you?
It affects Apache Software Foundation Apache Log4j 1.x and 28 other products. Add what you run to find out whether that includes you.
EPSS puts the chance of exploitation in the next 30 days at 66.54%, higher than 99% of scored CVEs. That is high: schedule it on your emergency patch path.
Do this next
Free account, 1 product
By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be included. This allows attackers to manipulate the SQL by entering crafted strings into input fields or headers of an application that are logged allowing unintended SQL queries to be executed. Note this issue only affects Log4j 1.x when specifically configured to use the JDBCAppender, which is not the default. Beginning in version 2.0-beta8, the JDBCAppender was re-introduced with proper support for parameterized SQL queries and further customization over the columns written to in logs. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.
- CVSS
- 9.8 CRITICAL (v3.1, CISA ADP)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Weakness (CWE)
- CWE-89
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- 66.54% (percentile 99)
- Assigned by
- apache
- NVD analysis
- Modified
- Record last updated
- May 27, 2026
- First seen by InfoSec Signals
- Oct 12, 2026
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.