Skip to main content
WordPress plugin recordReviewed

Akismet vulnerability history, API key status and Spam folder checks

Akismet checks comments and contact form submissions through a central service at Akismet.com, so a review covers more than the installed version: the key's status, the spam filtering choice and the privacy notice under comment forms.

Akismet vulnerability history

Source: Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . It lists 2 records for Akismet. Copyright notices, licence terms and a link to each source record are under Data source and licence at the foot of this page.

Update to at least version 3.1.5

Worked out from data retrieved on .

Every affected range listed in this source for Akismet ends before version 3.1.5.

A vendor can publish a security release before this source records it. Read the plugin's own changelog as well as this history.

  1. Akismet <= 3.1.4 - Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.1)
    Affected versions
    • All versions before 3.1.5

    Patched versions: 3.1.5

    Update to at least version 3.1.5.

  2. Akismet Spam Protection < 2.0.2 - Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.1)
    Affected versions
    • All versions up to and including 2.0.1

    Patched versions: 2.0.2

    Update to at least version 2.0.2.

Check Akismet on a live site

Read-only checks for a site you own or are authorised to review. Each step uses the WordPress dashboard or WP-CLI and sends no test payloads to the site.

What Akismet checks and what its service collects

Akismet Anti-spam: Spam Protection is published on WordPress.org by Automattic.

Its listing says it checks comments and contact form submissions against a global database of spam, and that once activated it prompts you to get an Akismet.com API key.

The plugin ships privacy policy text about visitors who comment on sites that use the Akismet Anti-spam service. It says the information collected depends on how Akismet is set up for the site, but typically includes the commenter's IP address, user agent, referrer and site URL, along with other information directly provided by the commenter such as their name, username, email address and the comment itself.

The listing speaks of moderators, who can see the number of approved comments for each user. WordPress's roles page gives an Administrator access to all administration features within a single site.

Akismet Cross-Site Scripting records and the names in their titles

The records in the history on this page are the ones the source data files under the WordPress.org slug akismet.

The titles quoted here use other names than the listing, which is headed Akismet Anti-spam: Spam Protection. The title of CVE-2007-2714 begins "Akismet Spam Protection" and that of CVE-2015-9357 begins "Akismet".

Both titles end "Cross-Site Scripting", and neither names a role. Match on the version fields. CVE-2015-9357 has "<= 3.1.4" in its title, while its affected versions field reads all versions before 3.1.5 and its patched versions field lists 3.1.5. For CVE-2007-2714 the fields read all versions up to and including 2.0.1, with 2.0.2 patched.

Some entries in the changelog on the WordPress.org listing, and in the changelog.txt file it points to for older entries, describe security changes in the vendor's own words. The records here are only what the source data holds, so read both before relying on the update guidance at the top of the history.

Reading Akismet on a site: version, key, Spam folder, forms and notice

Leave the Akismet settings screen without using Save changes or Disconnect this account: every check here reads a screen, on a site you are authorised to review.

Akismet version and update status

On the Plugins screen, the Description column includes the version number, and the Automatic update column holds the link that enables or disables auto-updates for the plugin. Look under the Inactive link too: Akismet's article on network setups calls it "the Akismet Plugin bundled with WP", so check for a copy even where nobody recalls installing one.

API key and subscription status

Akismet's activation guide says that on WordPress 7.0 or higher the key can be added at Settings > Connectors. On older versions it points to Settings > Akismet Anti-spam, or to Jetpack > Akismet Anti-spam if Jetpack is active. Akismet's article on network setups adds a WPCOM_API_KEY constant in wp-config.php, and says that once it is configured the API key field is not displayed on the settings screen.

The settings screen shipped with the plugin has an Account part with a Status, labelled Active, Cancelled, Suspended, Missing or No subscription found. Write down where the key is set and the status shown, but not the key. Note any comment whose history reads "Akismet was unable to check this comment but will automatically retry later."

Spam filtering choice and the Spam folder

On the settings screen shipped with the plugin, the Spam filtering row has two choices: "Silently discard the worst and most pervasive spam so I never see it." and "Always put spam in the Spam folder for review." Record which is selected and the number of days in the note under them, after which spam in the spam folder is deleted automatically.

Read Comments > Spam without clicking Spam or Not Spam: Akismet's training page says every time you mark a comment as spam or not spam you are teaching Akismet.

Comment forms and contact forms

Akismet's contact form guide says that once Akismet is activated it checks both blog comments and contact forms if you have them, and that it is not possible to activate it on one but not the other. Some integrations are automatic, it says, Jetpack's contact form among them; others need configuration, among them Contact Form 7, Gravity Forms, Ninja Forms and WPForms. List every public form, the plugin behind it, and whether Akismet is switched on for it there.

Privacy notice under comment forms

The Privacy row on the settings screen has two choices: "Display a privacy notice under your comment forms." and "Do not display privacy notice." Akismet's article on the notice says that if the akismet_comment_form_privacy_notice option is not yet set, the front-end notice will not be displayed, and describes a filter of the same name that overrides the option's value.

So record the choice, then open a post with a comment form and note whether the notice appears and where its link goes.

Akismet security settings a version match does not read

A version match shows exposure to a known record.

It does not show whether anyone used the flaw, and it reads none of the settings covered here. Add one more to that list: the settings screen shipped with the plugin has a Tool access row labelled "Allow MCP clients to access Akismet data and functionality". Record whether it is ticked, where your version shows it.

The listing's changelog says webhooks were enabled so that Akismet can process comments asynchronously. A WordPress security audit starts logged out, lists the REST routes under /wp-json/ and the admin-ajax actions that plugins register for logged-out visitors, and calls each one without a session. A route that changes data or returns settings to an anonymous request is a finding.

Frequently asked questions

Read the fields, not the titles. The title of CVE-2007-2714 has "< 2.0.2", and its affected versions field reads all versions up to and including 2.0.1, with 2.0.2 in its patched versions field. The title of CVE-2015-9357 has "<= 3.1.4", and its affected versions field reads all versions before 3.1.5. Once the fields are matched, read the update guidance at the top of the history.

The test Akismet's support page describes changes the site. The page says that as long as Akismet is properly registered and configured, a test phrase it gives can be entered as the text of a comment, that the submission will be accepted normally, and that you can confirm Akismet is working by checking that it was automatically filtered into the Spam tab at WP Admin > Comments > Spam. That step adds a comment to the site.

Akismet's page for server administrators gives the WordPress plugin's requirements as those of WordPress plus two: PHP's fsockopen and gethostbynamel functions must not be disabled, and the server needs TCP connectivity to akismet.com.

Akismet's support page on what it protects says that in WordPress it does not check spam user registrations, and that stopping registration spam needs an additional solution alongside Akismet. Whether strangers can register is a WordPress setting, Anyone can register, on the Settings > General screen.

Scope the right test for your application

Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.

Data source and licence

The vulnerability records on this page come from Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . The records contain material that is subject to copyright. Each copyright notice and its licence are reproduced once below, followed by a link to every source record.

Copyright 2012-2026 Defiant Inc.

Applies to every record listed below.

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

Copyright 1999-2026 The MITRE Corporation

Applies to every record listed below.

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.