Twigify <= 1.1.2 & AP Twig Bridge <= 1.0 & Content Template Engine <= 0.9.4 — Running Vulnerable Twig Package
82b78826-b256-4612-a830-d44a9bc97541Published · Updated Action summary
Twigify: Affected: ≤1.1.2No patch available
AP Twig Bridge: Affected: ≤1.0No patch available
Content Template Engine: Affected: ≤0.9.4No patch available
What to do until a fix ships- Severity
- High7.3
- CVSS
- 7.3CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:LWhat does this vector mean?
AV:NAttack vector- Network
AC:LAttack complexity- Low
PR:NPrivileges required- None
UI:NUser interaction- None
S:UScope- Unchanged
C:LConfidentiality- Low
I:LIntegrity- Low
A:LAvailability- Low
- Required access
- No account needed
- Exploit prediction (EPSS)
- No score
- CISA KEV
- Not listed
On this page7
Am I affected?
Twigify twigify
- Affected≤ 1.1.2
- PatchedNo fix yet
No patched version available.
You are affected if you run ≤ 1.1.2. No fixed version has been released.
AP Twig Bridge ap-twig-bridge
- Affected≤ 1.0
- PatchedNo fix yet
No patched version available.
You are affected if you run ≤ 1.0. No fixed version has been released.
Content Template Engine content-template-engine
- Affected≤ 0.9.4
- PatchedNo fix yet
No patched version available.
You are affected if you run ≤ 0.9.4. No fixed version has been released.
- Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Twigify.
- No admin access? Run a passive check of your site. It reads public files only.
- No account is needed to exploit this. Treat any exposed site on an affected version as at risk.
What to do
- No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
- No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
- No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
- Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
- Watch Twigify to get an email when the next vulnerability is published.
Advisory
Source description from Wordfence Intelligence, credited to Pierre Rudloff.
The Twigify plugin for WordPress is running a vulnerable version of Twig (1.16.3) in all versions up to, and including, 1.1.2, the AP Twig Bridge plugin for WordPress is running a vulnerable version of Twig (1.5.0) in all versions up to, and including, 1.0, and the Content Template Engine plugin for WordPress is running a vulnerable version of Twig (1.22.3) in all versions up to, and including, 0.9.4. This version of Twig contains many security vulnerabilities, though none have been confirmed exploitable in the Twigify or AP Twig Bridge plugins.
Exploits & references
Proof-of-concept & detection
No public proof-of-concept or detection template is known for this vulnerability.
Advisories & patches
- Advisorywordfence.com
Timeline
CVE published
Severity high, CVSS 7.3
Record last updated
Sources & licenses
- Vulnerability data
- Wordfence Intelligence. [object Object] Licensed under the CC BY-SA 4.0.
- CVSS / CWE
- National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
- VulnCrest content
- Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.