Skip to content

Update config.audit to config.policy #589

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
retlehs merged 1 commit into from
Jul 25, 2026
Merged

Update config.audit to config.policy #589

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions bedrock/auditing-wordpress-vulnerabilities-with-composer.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,10 +1,11 @@
---
date_modified: 2026-05-03 12:00
date_modified: 2026-07-24 23:00
date_published: 2026-05-03 12:00
description: Audit WordPress plugins and themes for known vulnerabilities with Composer using WP Sec Adv, a security advisory repository sourced from Wordfence Intelligence.
title: Auditing WordPress Vulnerabilities with Composer
authors:
- ben
- tangrufus
---

# Auditing WordPress Vulnerabilities with Composer
Expand Down Expand Up @@ -45,11 +46,10 @@ Not every advisory requires immediate action. Composer lets you acknowledge spec
```json
{
"config": {
"audit": {
"ignore": {
"CVE-2026-3589": {
"apply": "block",
"reason": "Waiting for upstream fix in v1.2.3. Allow during updates but still report in audits"
"policy": {
"advisories": {
"ignore-id": {
"CVE-2026-3589": "Waiting for upstream fix in v1.2.3. Allow during updates but still report in audits"
}
}
}
Expand Down
Loading