CVE-2024-7687: The AZIndex WordPress plugin through 0.8.1 does not have CSRF check in some places, and is missing sanitisatio

Q: How do I fix CVE-2024-7687?

azindex: upgrade to newer than 0.8.1. Exact commands for each OS are on this page.

Q: Is CVE-2024-7687 being exploited?

CVE-2024-7687 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2024-7687 affect?

CVE-2024-7687 affects azindex. Severity is medium (CVSS 4.3). The AZIndex WordPress plugin through 0.8.1 does not have CSRF check in some places, and is missing sanitisation as well as escaping, which could allow attackers to make logged in admin add Stored XSS payloads via a CSRF attack.

Q: How urgent is CVE-2024-7687?

Priority 22/100. Public exploit reference

Routine

MEDIUM 4.3UPGRADE

CVE-2024-7687 is a medium-severity flaw (CVSS 4.3) affecting azindex. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The AZIndex WordPress plugin through 0.8.1 does not have CSRF check in some places, and is missing sanitisation as well as escaping, which could allow attackers to make logged in admin add Stored XSS payloads via a CSRF attack.

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	4.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.2% (top 92%)
CISA exploited list	No
Weakness	CWE-352, CWE-79
Published	2024-09-09
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: azindex project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-09-09 06:15 UTCPublished CVE record published
2026-06-17 08:20 UTCUpdated Record last modified

azindex project azindex UPGRADE

Affected: <= 0.8.1

Fixed in: newer than 0.8.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy azindex || rpm -q azindex || azindex --version

2. UPGRADE to newer than 0.8.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade azindex

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade azindex

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-7687?

azindex: upgrade to newer than 0.8.1. Exact commands for each OS are on this page.

Is CVE-2024-7687 being exploited?

CVE-2024-7687 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-7687 affect?

CVE-2024-7687 affects azindex. Severity is medium (CVSS 4.3). The AZIndex WordPress plugin through 0.8.1 does not have CSRF check in some places, and is missing sanitisation as well as escaping, which could allow attackers to make logged in admin add Stored XSS payloads via a CSRF attack.

How urgent is CVE-2024-7687?

Priority 22/100. Public exploit reference

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2024-7688 MEDIUM 6.5 UPGRADE The AZIndex WordPress plugin through 0.8.1 does not have CSRF checks in some places, which could allow attacke

References

← Back to latest CVEs