CVE-2013-10020: A vulnerability, which was classified as problematic, was found in MMDeveloper A Forms Plugin up to 1.4.2 on W

Q: How do I fix CVE-2013-10020?

a-forms: upgrade to 1.4.3. Exact commands for each OS are on this page.

Q: Is CVE-2013-10020 being exploited?

CVE-2013-10020 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-2013-10020 affect?

CVE-2013-10020 affects a-forms. Severity is low (CVSS 3.5). A vulnerability, which was classified as problematic, was found in MMDeveloper A Forms Plugin up to 1.4.2 on WordPress. This affects an unknown part of the file a-forms.php. The manipulation leads to cross site scripting. It is possible to

Q: How urgent is CVE-2013-10020?

Priority 24/100. No elevated risk signals yet.

Routine

LOW 3.5UPGRADE

CVE-2013-10020 is a low-severity flaw (CVSS 3.5) affecting a-forms. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A vulnerability, which was classified as problematic, was found in MMDeveloper A Forms Plugin up to 1.4.2 on WordPress. This affects an unknown part of the file a-forms.php. The manipulation leads to cross site scripting. It is possible to initiate the attack remotely. Upgrading to version 1.4.3 is able to address this issue. The identifier of the patch is 3e693197bd69b7173cc16d8d2e0a7d501a2a0b06. It is recommended to upgrade the affected compone

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	3.5 (Low)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	Required
EPSS exploit chance	0.6% (top 52%)
CISA exploited list	No
Weakness	CWE-79
Published	2023-03-10
Last modified	2026-06-16

Publisher (CNA): VulDB · Vendor: a-forms project

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

Am I affected?

Timeline

2023-03-10 01:15 UTCPublished CVE record published
2026-06-16 23:50 UTCUpdated Record last modified

a-forms project a-forms UPGRADE

Affected: < 1.4.3

Fixed in: 1.4.3

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy a-forms || rpm -q a-forms || a-forms --version

2. UPGRADE to 1.4.3 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade a-forms

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade a-forms

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-2013-10020?

a-forms: upgrade to 1.4.3. Exact commands for each OS are on this page.

Is CVE-2013-10020 being exploited?

CVE-2013-10020 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-2013-10020 affect?

CVE-2013-10020 affects a-forms. Severity is low (CVSS 3.5). A vulnerability, which was classified as problematic, was found in MMDeveloper A Forms Plugin up to 1.4.2 on WordPress. This affects an unknown part of the file a-forms.php. The manipulation leads to cross site scripting. It is possible to

How urgent is CVE-2013-10020?

Priority 24/100. No elevated risk signals yet.

Software pages

WordPress vulnerabilities · PHP vulnerabilities

References

← Back to latest CVEs